The mock is nw the default, the old dev file was of no use outside the 
setup project, so it is kept there now.

The latest image is not actually used anywhere so can be removed for 
now. The tagged image process was faulty. This makes it so, that the 
tagged build is only run on special tag CI-runs.

This is only used within the build so can be discarded soon after.

The backend address in the environment file needs to either be localhost 
for using the app from the (host system's) browser of the internal 
docker name (backend-mock) so the frontend container can reach it. SO 
the testcenterUrl can either be reached from the host or fromt he 
frontend container but not both. This makes it so, that the e2e tests 
use a specific environment (defined in angular.json) which uses a 
different environment file for running e2e test within the frontend 
container.

instad the internal one

because environment.ts would be missing otherwise

copy paste error

There were errors on the console about unfound backend paths. No the 
test fails when such errors appear.

Now we again have a dev and prod variant and the user needs to run 'make 
init-dev-config'at first time setup.

Was no AND condition before.

This obviously needs to be in for new developers.

upgrades eslint ruleset to version 0.0.9 and removes `eslint-disable-next-line no-param-reassign`-exception where it it is possible

This makes 'em not block the console window.

This should be a separate step for logic reasons.