hive: Add --sim.exactmatch flag

[spencer-tb]

Description

Following this PR: #929

On occasion we may use a regex pattern that will run more tests than intended.

The intention behind the sim.limit below may be to solely run a single test in isolation:

... --sim.limit engine-cancun/"InvalidPayloadAttributes: Missing BeaconRoot" --docker.output

Due to the increasing number of tests within the engine simulator alongside its programtic naming of tests, the above sim.limit will run and additional test using regex matching:

InvalidPayloadAttributes: Missing BeaconRoot
InvalidPayloadAttributes: Missing BeaconRoot (Syncing)

Updated Proposed Change

Adds an additional boolean flag: --sim.exactmatch, that can be used to escape and anchor the regex expression specified within --sim.limit.

[spencer-tb]

@danceratopz @marioevz - is this valuable? Maybe useful for non-consume based simulators. Otherwise I can update the docs to show how you can use regex correctly for exact matches within --sim.limit.

[danceratopz]

@danceratopz @marioevz - is this valuable? Maybe useful for non-consume based simulators. Otherwise I can update the docs to show how you can use regex correctly for exact matches within --sim.limit.

I definitely think this is useful, for now, we've added this functionality to the eest/consume-* simulators via some helper syntax in --sim.limit: The id: prefix tells --sim.limit to only run the single test case (it still does a regex match, but escapes the provided test case id for the user):

--sim.limit "id:tests/prague/eip2935_historical_block_hashes_from_state/test_block_hashes.py::test_block_hashes_history[fork_Prague-blockchain_test-full_history_plus_one_check_blockhash_first]"

So far we've had positive feedback from devs using this. Having consistent behavior across simulators with --sim.exactmatch would be preferable though.