Test with DEBUGGING inactive

Follow-up issue of #335 (closed).

The DEBUGGING switch is meant to globally control features for easier debugging and experimentation in the code. It is active per default and provides e.g. capabilities to simulate frameloss at the command line (-fec) or force specific core coder/stereo modes (-force). For the final delivery, it should be deactivated or probably even stripped out of the code.

As delivery is approaching, we should migrate to testing the code that is going to be delivered instead of the debug code. A first step is done in #335 (closed) which will remove the use of some -force* switches from self_test.prm. Other immediate todos are:

• instead of using -fec XX for frameloss simulation, add the errors to the bitstream directly using eid-xor. For this to be reproducible, we need to store some frame error patterns with the corresponding error probabilities. Also, the test script probably needs to be adapted in a similar fashion as was necessary for the network simulator. -> addressed in #905 (closed)
• in the test jobs itself, one needs to either deactivate DEBUGGING via script or shell command, OR: have DEBUGGING deactivated by default in the repo -> addressed in #905 (closed)
• As a sanity check, a BE comparison between DEBUGGING on and off should be done once. If we decide to actually have DEBUGGING deactivated per default, the corresponding merge request pipelines would serve as this sanity check.