Cardano Updates

Move deterministic budget values (cpu_budget, memory_budget, memory_bytes) to the top level of JSON output. Keep only variable timing data in the timing_samples array. This eliminates redundant data that was repeated identically in every measurement sample.

Previous structure stored budget in each sample, wasting space and obscuring the deterministic nature of budget values. New structure clearly separates deterministic (budget) from variable (timing) data.

Add explicit tests verifying the deterministic nature of CEK evaluation
and proper error type mapping for runtime failures.

- Budget determinism: verify all samples have identical cpu/memory budget
- Evaluation error: verify runtime errors produce evaluation_error type
- Adjust range assertions for real (small) values vs mock ranges

Replace random mock measurements with actual UPLC evaluation using
the CEK machine from plutus-core. Programs are parsed, converted to
NamedDeBruijn representation, and evaluated with budget tracking.

Key changes:
- Parse textual UPLC via UntypedPlutusCore.Parser
- Evaluate with runCekDeBruijn using tallying mode
- Extract deterministic CPU/memory budgets from ExBudget
- Collect 15 timing samples with criterion-measurement
- Map parse errors to syntax_error, runtime errors to evaluation_error

Add uplc-evaluator to exposed-haskell-packages in nix/outputs.nix to make
it available via nix build/run commands.

This allows users to easily build and use the uplc-evaluator service:
  nix build .#uplc-evaluator
  nix run .#uplc-evaluator -- --help

The executable provides an asynchronous file-based interface for
benchmarking UPLC programs, as specified in plutus-benchmark/uplc-evaluator/SPEC.md.

Add uplc-evaluator to exposed-haskell-packages in nix/outputs.nix to make
it available via nix build/run commands.

This allows users to easily build and use the uplc-evaluator service:
  nix build .#uplc-evaluator
  nix run .#uplc-evaluator -- --help

The executable provides an asynchronous file-based interface for
benchmarking UPLC programs, as specified in plutus-benchmark/uplc-evaluator/SPEC.md.

The test harness was searching for the uplc-evaluator executable only in
hardcoded dist-newstyle paths with specific GHC versions. This failed in
nix builds where the executable is made available via build-tool-depends
in PATH.

Solution: Use System.Directory.findExecutable to locate uplc-evaluator
in PATH. This works for both:
- cabal builds: cabal test adds build-tools to PATH
- nix builds: nix adds dependencies to PATH via build-tool-depends

This eliminates the need to maintain a list of hardcoded paths for
different platforms and GHC versions.

Document the variable capture bug fix in the changelog.

Add 8 test cases covering variable capture scenarios in dischargeCekValue:

- Free variables under 1, 2, and 3 lambdas

- Deeply indexed free variables

- Multiple free variables in the same term

- Nested environment structures

Tests verify that free variables are correctly shifted to prevent capture when terms are discharged from the evaluation environment.

Tests for #7526

Add shiftTermBy function to correctly shift free variables when discharging values from the environment. Previously, free variables in discharged terms could be captured by outer lambdas, causing incorrect variable references in the output term.

The fix tracks binding depth during discharge and shifts free variables (those with indices beyond the current binding depth) by the appropriate amount to maintain correct scoping.

Resolves #7526