feat(forge): make solar analysis optional in test runner

[decofe]

Summary

Decouple the test runner from requiring Solidity-specific internals, enabling non-Solidity compilers to use Foundry's fuzzing/testing/cheatcode infrastructure.

Motivation

Tweet thread from @real_philogy requesting the ability to plug a custom compiler into Foundry. Companion to foundry-rs/compilers#368.

Changes

Core: analysis made optional

• MultiContractRunner.analysis: Arc<solar::sema::Compiler> → Option<Arc<...>>
• TestRunnerConfig::executor: conditionally calls set_analysis only when Some

New compiler-agnostic entry point

• PreLinkedArtifacts struct — bundles deployable contracts, known contracts, libs, fuzz literals, and inline config
• MultiContractRunnerBuilder::build_from_artifacts() — builds a test runner from pre-linked artifacts directly, bypassing ProjectCompileOutput, solar, and the linker entirely

Bridge types (local mirrors of foundry-compilers types)

• FuzzLiteral enum + LiteralsDictionary::from_fuzz_literals(literals, max_values) — converts compiler-provided literals to LiteralMaps with the same semantics as the solar path (uint/int width fan-out, string hashing, right-padding, max cap)
• InlineConfigEntry + InlineConfig::from_entries(entries, profiles) — converts compiler-provided config overrides to NatSpec-based InlineConfig
• LiteralsDictionary::from_maps() — direct constructor from pre-built LiteralMaps
• InlineConfig::from_natspecs() — constructor from pre-parsed NatSpec entries

No behavior change

The standard Solidity path still populates all fields via the existing build() method.

Testing

cargo check -p forge and cargo clippy -p forge -p foundry-config -p foundry-evm-fuzz -- -D warnings pass.

How a non-Solidity compiler would use this

// 1. Compile your language to ABI + bytecode
let (deployable, known, libs) = my_compiler.compile_and_link(sources)?;

// 2. Optionally extract fuzz literals from your AST
let fuzz_dict = LiteralsDictionary::from_fuzz_literals(my_literals, max_values);

// 3. Optionally provide per-test config
let inline_cfg = InlineConfig::from_entries(my_config_entries, &profiles)?;

// 4. Build the runner — fuzzing, cheatcodes, invariant testing all work
let runner = MultiContractRunnerBuilder::new(config)
    .build_from_artifacts(
        PreLinkedArtifacts {
            deployable_contracts: deployable,
            known_contracts: known,
            libs_to_deploy: libs,
            fuzz_literals: fuzz_dict,
            inline_config: inline_cfg,
        },
        evm_env, tx_env, evm_opts,
    )?;

Next steps

• Add integration test exercising the build_from_artifacts path with analysis: None
• Once foundry-compilers publishes TestRunnerSupport trait, replace local FuzzLiteral/InlineConfigEntry mirrors with re-exports

Prompted by: zerosnacks