CCIP-3461: Optimize mainnet scheduled test

[b-gopalswami]

Motivation

Optimize the resource and fund consumption of the mainnet soak test. Currently, the mainnet soak test runs every six hours in Kubernetes, executing one CCIP transaction per hour for a duration of five hours across 28 bidirectional lanes. This setup is designed to provide consistent observability data on the CCIP mainnet, allowing us to differentiate between service outages and quiet periods. However, these tests are inefficient, consuming Kubernetes resources and significant mainnet funds.

Ideas:

1. Discussion thread is initiated with o11y team and decided that it's not required to create txs for every hour instead create one tx if there are no activity for last 24h.
2. Convert to smoke test as we are planning to fire only one request instead of Soak test.
3. Converting to smoke will elevate the K8 resource consumption as the test will run using github runner.

Solution

• 1. Modify the pipeline to run it as smoke test
• 2. Add traffic check to smoke test
• 3. Add new set of additional 21 lanes and resulted in total of 49 lanes. (i.e 98 unique lanes)
• 5. Add RPCs, Wallet key for new lanes to test secrets
• 6. Load funds for new lanes
• 7. Schedule pipeline to run for every 6hrs

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube