Change default `meltano config` behavior to `--no-environment`

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3503

Originally created by @aaronsteers on 2022-05-18 03:06:00

---

I keep running into this and I think it’s worth reconsidering the defaults here.

In CI - my CLI commands looked fine and only after 'cat’ing my meltano.yml file was I able to diagnose the issue here.

$ meltano config tap-gitlab set _pip_url git+https://github.com/MeltanoLabs/tap-gitlab.git@main
2022-05-18T00:23:28.361467Z [info     ] Environment 'dev' is active
Extractor 'tap-gitlab' setting '_pip_url' was set in `meltano_environment`: 'git+https://github.com/MeltanoLabs/tap-gitlab.git@main'
$ cat meltano.yml
version: 1
default_environment: dev
send_anonymous_usage_stats: false
plugins:
  extractors:
  - name: tap-gitlab
    variant: meltanolabs
    pip_url: git+https://github.com/MeltanoLabs/tap-gitlab.git
environments:
- name: dev
  config:
    plugins:
      extractors:
      - name: tap-gitlab
        pip_url: git+https://github.com/MeltanoLabs/tap-gitlab.git@main

This one is particularly sticky because ‘pip_url’ at the environment level seems to be a noop.

[DouweM]

@aaronsteers The top-level specific issue is https://github.com/meltano/meltano/issues/6101.

[DouweM]

@aaronsteers Note that setting pip_url using meltano config <plugin> set _pip_url <url> is not actually expected to work at all, as it’s not a plugin extra or setting, but a key plugin definition property. If we document that anywhere, we shouldn’t. It’s not working under environments because it wasn’t meant to.