Fix: Temporarily disable env var arguments for boolean default-true/exclusive flags

[amcaplan]

WHY are these changes introduced?

Apparently these never worked anyway for boolean flags before oclif 1.16.1. Then they started working, but only to specify true; otherwise, they essentially force a false as though it were specified.

More details: oclif/core#536

WHAT is this pull request doing?

Comments out the env-sourced way to set these boolean flags.

How to test your changes?

$ shopify app dev --path=fixtures/app --tunnel-url=https://my-tunnel-url:port

On main you get this error:

╭─ error ──────────────────────────────────────────────────────────────────────╮
│                                                                              │
│  The following errors occurred:                                              │
│    --tunnel-url=https://my-tunnel-url:port cannot also be provided when      │
│  using --no-tunnel                                                           │
│    --tunnel-url=https://my-tunnel-url:port cannot also be provided when      │
│  using --tunnel                                                              │
│  See more help with --help                                                   │
│                                                                              │
╰──────────────────────────────────────────────────────────────────────────────╯

On this branch, the command proceeds successfully.

Measuring impact

How do we know this change was effective? Please choose one:

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
• Existing analytics will cater for this addition
• PR includes analytics changes to measure impact

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

[github-actions]

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run "yarn changeset add" to track your changes and include them in the next release CHANGELOG.

[alvaro-shopify]

• In case we revert Upgrade TS 4.84, OCLIF 1.16.4 will also do the trick?.
• is it better to revert and wait for the oclif fix to be solved?

[amcaplan]

@alvaro-shopify there's little benefit to reverting that upgrade, as previously none of the env settings for boolean flags were working. (Support for that was introduced in 1.16.1... it just also happened to break these flags.) So the functionality is better with the sum total change than without it.

[amcaplan]

Closing in favor of #666