Adding CTF v2 approach to run the anvil chains

[b-gopalswami]

This PR is an initial attempt to implement CTF v2 features. Have tested TestTransferToken primarily and it runs fine with this implementation. Haven't run all other test and there might be some missing pieces as well. Making this work across all the test has to be separate work.

At this point, the speed comparison looks better in terms of network and required contract deployment setup however the CCIP transaction is bit slower and the overall execution time slightly more than docker.
Setup time is less by ~40-50 seconds. Overall time is increased by ~30s.

Needs further investigation to understand why it takes more time in finding the commit report event and execution status changed event.

The key features from CTF v2 to note:

1. Anvil chains
2. Ability for local observability (need ctf CLI, refer test setup here)
3. 0s block and periodic mining control
4. Enriched mocks

To run the test with this approach, set these env variables.
CCIP_V16_TEST_ENV=anvil-docker; CTF_CONFIGS=../../testconfig/ccip/ccip-default-ctfv2.toml

To spin up local observability,
Run ctf obs u for grafana;
Run ctf bs u for blockscout

[github-actions]

AER Report: CI Core ran successfully ✅

aer_workflow , commit

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

[github-actions]

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[cl-sonarqube-production]

Quality Gate passed

Issues
4 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
5.0% Duplication on New Code

See analysis details on SonarQube