This PR adds a band-aid to a long-standing issue that config.dirs is used when running CLI commands.

This caused localstack to create the .filesystem directory in the Python path, which was originally just designed for executing host mode in developer environments, even when simply using the CLI.

 % locate .filesystem     
/home/thomas/.pyenv/versions/3.10.9/lib/python3.10/site-packages/.filesystem
/home/thomas/workspace/localstack/localstack/.filesystem
/home/thomas/workspace/localstack/localstack-ext/.venv/lib/python3.10/site-packages/.filesystem

Because the CLI and the runtime share control paths, there are situations where values from config.dirs are used to create directories or files, even though they may not make sense in the context of the CLI.

• dirs.cache is used by the analytics metadata (cache machine id file), and was used by the get_service_catalog call (now removed)
• dirs.data is used by localstack_ext.config (this will be removed)
• dirs.logs is used as target to put the logs of the docker run command when starting localstack
• dirs.tmp should be removed now, but left it in there just in case

There is now a special control path that populates config.dirs deliberately with values that make the above examples work without the .filesystem directory.
To reduce the number of calls to config.dirs, I also removed some unused code from the startup procedure.

Once the old edge proxy logic is removed, we can more easily split up infra.py and therefore bootstrap.py, which will hopefuly also make it easier to separate out the CLI code.