[CLI] Add compiler-message-format-json experiment value to aptos move compile and aptos move lint

[mkurnikov]

Description

Adds an compiler experiment flag compiler-message-format-json to replace codespan formatted compiler errors with structured unformatted JSON.

aptos move compile --experiments compiler-message-format-json

It's supposed to only be consumed by the other tools like IDEs.

How Has This Been Tested?

Added a couple of tests to move-compiler-v2/tests/compiler-message-format-json.

Key Areas to Review

Adds Emitter trait, which has two impls, HumanEmitter and JsonEmitter. HumanEmitter just wraps the existing codespan_reporting::term::emit() calls, and it's a default, so there should be no changes to the existing tests.
JsonEmitter serializes compiler errors in the json format for external tools (i.e. Move on Aptos Intellij plugin) to use. It's enabled with the Experiment::MESSAGE_FORMAT_JSON.

Type of Change

• New feature
• Bug fix
• Breaking change
• Performance improvement
• Refactoring
• Dependency update
• Documentation update
• Tests

Which Components or Systems Does This Change Impact?

• Validator Node
• Full Node (API, Indexer, etc.)
• Move/Aptos Virtual Machine
• Aptos Framework
• Aptos CLI/SDK
• Developer Infrastructure
• Move Compiler
• Other (specify)

Checklist

• I have read and followed the CONTRIBUTING doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I identified and added all stakeholders and component owners affected by this change as reviewers
• I tested both happy and unhappy path of the functionality
• I have made corresponding changes to the documentation

[trunk-io]

⏱️ 11s total CI duration on this PR

Job	Cumulative Duration	Recent Runs
permission-check	6s	🟥 🟥
permission-check	5s	🟥 🟥

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

[vineethk]

I have left some more comments, but this is looking good in general.

Could you please update the PR description regarding whether this is still a WIP, and any notes on testing?

[mkurnikov]

@vineethk Thanks for the review! I addressed your comments, changed the description and added some tests.

[vineethk]

LGTM!

[vineethk]

@mkurnikov Looks like the lint checks are failing because of missing license headers: https://github.com/aptos-labs/aptos-core/actions/runs/12445881990/job/34799996744?pr=15540. Could you please add the following to the top of the newly added source files:

// Copyright © Aptos Foundation
// SPDX-License-Identifier: Apache-2.0

[github-actions]

✅ Forge suite compat success on 6593fb81261f25490ffddc2252a861c994234c2a ==> 8aa53e8937a4b027fe226b65d57e6524db308188

Compatibility test results for 6593fb81261f25490ffddc2252a861c994234c2a ==> 8aa53e8937a4b027fe226b65d57e6524db308188 (PR)
1. Check liveness of validators at old version: 6593fb81261f25490ffddc2252a861c994234c2a
compatibility::simple-validator-upgrade::liveness-check : committed: 18333.54 txn/s, latency: 1903.25 ms, (p50: 1800 ms, p70: 2100, p90: 2400 ms, p99: 2700 ms), latency samples: 594800
2. Upgrading first Validator to new version: 8aa53e8937a4b027fe226b65d57e6524db308188
compatibility::simple-validator-upgrade::single-validator-upgrading : committed: 8235.59 txn/s, latency: 3678.33 ms, (p50: 3700 ms, p70: 3900, p90: 4200 ms, p99: 4300 ms), latency samples: 149020
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 8320.61 txn/s, latency: 3954.24 ms, (p50: 4200 ms, p70: 4300, p90: 4300 ms, p99: 4600 ms), latency samples: 286440
3. Upgrading rest of first batch to new version: 8aa53e8937a4b027fe226b65d57e6524db308188
compatibility::simple-validator-upgrade::half-validator-upgrading : committed: 8444.80 txn/s, latency: 3534.54 ms, (p50: 3900 ms, p70: 4200, p90: 4600 ms, p99: 4700 ms), latency samples: 157020
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 8456.58 txn/s, latency: 3955.58 ms, (p50: 4300 ms, p70: 4400, p90: 4500 ms, p99: 4900 ms), latency samples: 281060
4. upgrading second batch to new version: 8aa53e8937a4b027fe226b65d57e6524db308188
compatibility::simple-validator-upgrade::rest-validator-upgrading : committed: 12624.25 txn/s, latency: 2325.96 ms, (p50: 2600 ms, p70: 2800, p90: 2900 ms, p99: 2900 ms), latency samples: 218480
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 5511.70 txn/s, submitted: 5511.85 txn/s, expired: 0.15 txn/s, latency: 2600.07 ms, (p50: 2700 ms, p70: 2800, p90: 2900 ms, p99: 2900 ms), latency samples: 403749
5. check swarm health
Compatibility test for 6593fb81261f25490ffddc2252a861c994234c2a ==> 8aa53e8937a4b027fe226b65d57e6524db308188 passed
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Validator CPU Profile
• Fullnode CPU Profile
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite realistic_env_max_load success on 8aa53e8937a4b027fe226b65d57e6524db308188

two traffics test: inner traffic : committed: 15378.04 txn/s, latency: 2588.29 ms, (p50: 2600 ms, p70: 2700, p90: 2700 ms, p99: 3600 ms), latency samples: 5847040
two traffics test : committed: 99.97 txn/s, latency: 1307.75 ms, (p50: 1300 ms, p70: 1300, p90: 1400 ms, p99: 1700 ms), latency samples: 1800
Latency breakdown for phase 0: ["MempoolToBlockCreation: max: 1.520, avg: 1.485", "ConsensusProposalToOrdered: max: 0.280, avg: 0.279", "ConsensusOrderedToCommit: max: 0.289, avg: 0.285", "ConsensusProposalToCommit: max: 0.568, avg: 0.563"]
Max non-epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 0.52s no progress at version 2875 (avg 0.19s) [limit 15].
Max epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 0.57s no progress at version 1077991 (avg 0.55s) [limit 16].
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Validator CPU Profile
• Fullnode CPU Profile
• Test runner output
• Test run is land-blocking