Feature: Support bubbling up Precompile error messages

[mablr]

Motivation

This PR enhances precompile error reporting and closes #2898.

Solution

Attempt to implement a mechanism that records potential precompile error in context if depth == 0, in order to bubble it up in output as Bytes. Idea proposed by Rakita #2905 (review).

TODO

• make tests
• doc

[codspeed-hq]

CodSpeed Performance Report

Merging #2905 will degrade performances by 3.18%

_{Comparing mablr:feature/precompileerror-value-variant-without-copy-trait (0b4d66c) with main (0e05a30)}

Summary

❌ 1 regression
✅ 172 untouched

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
❌	transfer_finalize	15.1 µs	15.6 µs	-3.18%

[rakita]

We should have a different approach for this. Only place where we can return the error outside of evm is if transaction target points to the precompile.

We should introduce the mechanism that if depth == 0 and precompile returns the error for this error to be saved in Context and returned in output

[rakita]

Nits left, otherwise lgtm