[cli] Force global config file

[gregnazario]

Description

Right now, we can't change the default on the global config, because no one has a file to fall back on. So, this forces the file to show up, and then we can change the default afterwards.

Test Plan

[trunk-io]

⏱️ 11h 13m total CI duration on this PR

Job	Cumulative Duration	Recent Runs
rust-unit-tests	7h 9m	🟥 🟩 🟥 🟩
windows-build	1h 17m	🟩 🟩 🟩
rust-smoke-tests	28m	🟩
rust-lints	26m	🟩 🟩 🟩
execution-performance / single-node-performance	19m	🟩
run-tests-main-branch	17m	🟩 🟥 🟥
forge-e2e-test / forge	14m	🟩
rust-images / rust-all	13m	🟩
check	13m	🟩 🟩 🟩
forge-compat-test / forge	11m	🟩
cli-e2e-tests / run-cli-tests	7m	🟩
general-lints	7m	🟩 🟩 🟩
check-dynamic-deps	6m	🟩 🟩 🟩
semgrep/ci	2m	🟩 🟩 🟩
file_change_determinator	54s	🟩 🟩 🟩
node-api-compatibility-tests / node-api-compatibility-tests	48s	🟩
file_change_determinator	38s	🟩 🟩 🟩
execution-performance / file_change_determinator	13s	🟩
file_change_determinator	12s	🟩
permission-check	10s	🟩 🟩 🟩
permission-check	9s	🟩 🟩 🟩
permission-check	8s	🟩 🟩 🟩
permission-check	7s	🟩 🟩 🟩
determine-docker-build-metadata	3s	🟩
permission-check	2s	🟩

🚨 2 jobs on the last run were significantly faster/slower than expected

Job	Duration	vs 7d avg	Delta
run-tests-main-branch	6m	4m
windows-build	27m	20m

_{settings ⋅ feedback ⋅ docs ⋅ learn more about trunk.io}

[banool]

You mentioned that this may fail for permissions reasons. I can think of some situations where that might indeed happen. So maybe this should be best effort?

[github-actions]

✅ Forge suite compat success on aptos-node-v1.9.5 ==> b6a78bc059a68706261193303e00711da86da733

Compatibility test results for aptos-node-v1.9.5 ==> b6a78bc059a68706261193303e00711da86da733 (PR)
1. Check liveness of validators at old version: aptos-node-v1.9.5
compatibility::simple-validator-upgrade::liveness-check : committed: 6616 txn/s, latency: 4836 ms, (p50: 4800 ms, p90: 5400 ms, p99: 8100 ms), latency samples: 251420
2. Upgrading first Validator to new version: b6a78bc059a68706261193303e00711da86da733
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 925 txn/s, latency: 29981 ms, (p50: 35900 ms, p90: 42900 ms, p99: 44900 ms), latency samples: 56460
3. Upgrading rest of first batch to new version: b6a78bc059a68706261193303e00711da86da733
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 421 txn/s, submitted: 649 txn/s, expired: 228 txn/s, latency: 32549 ms, (p50: 32300 ms, p90: 57900 ms, p99: 68900 ms), latency samples: 37918
4. upgrading second batch to new version: b6a78bc059a68706261193303e00711da86da733
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 2919 txn/s, latency: 10506 ms, (p50: 9800 ms, p90: 17800 ms, p99: 18400 ms), latency samples: 134280
5. check swarm health
Compatibility test for aptos-node-v1.9.5 ==> b6a78bc059a68706261193303e00711da86da733 passed
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite realistic_env_max_load success on b6a78bc059a68706261193303e00711da86da733

two traffics test: inner traffic : committed: 7158 txn/s, latency: 5474 ms, (p50: 5100 ms, p90: 7200 ms, p99: 12300 ms), latency samples: 3099600
two traffics test : committed: 100 txn/s, latency: 2031 ms, (p50: 1900 ms, p90: 2200 ms, p99: 6100 ms), latency samples: 1800
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.229, avg: 0.203", "QsPosToProposal: max: 0.437, avg: 0.250", "ConsensusProposalToOrdered: max: 0.567, avg: 0.535", "ConsensusOrderedToCommit: max: 0.348, avg: 0.333", "ConsensusProposalToCommit: max: 0.891, avg: 0.868"]
Max round gap was 1 [limit 4] at version 1486663. Max no progress secs was 4.000021 [limit 15] at version 1486663.
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Test runner output
• Test run is land-blocking