[TASK] Allow execution of acceptance tests with local chromedriver

A local instance can sometimes be easier to debug and browser issues
can be introspected, when acceptance tests are possible to be run on
the host instead of in containers only.

Allow to run acceptance tests against a local server using a local
chromedriver. Also avoid the usage of precalculated session hashes,
which has no clear advantage, but requires codecept to perform
database connections directly: The tests now login via the backend
login form instead and store the session cookies between test runs.

As a side effect the codeception suites are cleaned up, to use
more efficient module config, instead of redundantly repeating
all WebDriver settings for headless and non-headless environment.

To execute codeception with local chromedriver against a custom
server URL run:

  chromedriver --silent & # use `killall chromedriver` when done

  typo3TestingAcceptanceBaseUrl=https://mycore.example.com/ \
  typo3TestingAcceptanceAdminPassword=...