set catalog feature flag for integration tests (init)

[mkenigs]

• Copy any tests in init.bats, python.bats, node.bats, and go.bats that are impacted by the catalog and run them with the catalog feature flag set. Make any small changes required to get them passing
• Set FLOX_FEATURES_USE_CATALOG=true and _FLOX_USE_CATALOG_MOCK="$TESTS_DIR/catalog_responses/empty_responses.json" for any other tests in the files to assert that they don't depend on the catalog
• If anything that isn't minor breaks, skip copied tests and create followup tickets

[dcarley]

Notes from refinement:

• There is one Python test in init.bats that should be moved to python.bats
• The rest of init.bats shouldn't depend on the catalog.
• All of the language auto-setup tests auto-install packages from the catalog

[mkenigs]

* There is one Python test in `init.bats` that should be moved to `python.bats`

The reason that one is in init.bats is because it's checking init and particularly FLOX_ENV_CACHE works for different types of environments (path, managed, remote). All of the language specific functional tests only use path environments. I'm not sure that's the most useful distinction but that's the reason