set catalog feature flag for integration tests (environment-remote)

[mkenigs]

• Copy any tests in environment-remote.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=/dev/null for all other tests in the file
• If anything that isn't minor breaks, skip copied tests and create followup tickets

[mkenigs]

All of the following tests need to be modified to work with the catalog because they're all performing installs. I think we can probably just get rid of the install for some of the trust tests, but we'll need to add mock response for most of these

• r0: building a remote environment creates outlink
• m1: install a package to a remote environment
• m2: uninstall a package from a managed environment
• m3: edit a package from a managed environment
• m9: activate works in remote environment
• m10.0: 'activate --remote' fails if remote environment is not trusted
• m10.1: 'activate --remote --trust' succeeds
• m10.2: 'activate --remote' succeeds if trusted by config
• m10.3: 'activate --remote' fails if denied by config, --trust overrides
• sanity check upgrade works for remote environments