Example minimal pipeline for smoke/load/chaos + Pumba chaos tool wrapper

[skudasov]

---

Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.

Why

The changes include adding new test configurations and implementations for smoke, load, and chaos testing scenarios using Chainlink nodes. The configurations specify the blockchain setup, data provider, and node set details required for the tests. The test implementations leverage the Chainlink testing framework to orchestrate the setup and execute different types of tests to ensure the Chainlink nodes' reliability, performance, and resilience under various conditions.

What

• Added smoke.toml, load.toml, and chaos.toml configuration files for defining test setups for smoke, load, and chaos testing scenarios respectively.
• Implemented smoke_test.go, load_test.go, and chaos_test.go to perform the actual tests using the Chainlink testing framework. These tests include setting up the blockchain network, data provider, and Chainlink nodes as specified in the configuration files.
• Introduced gun.go to define custom "gun" implementations for firing requests to Chainlink nodes during the tests, specifically targeting the bridges API endpoint in the bridges mode.
• Added .envrc and go.mod files for environment configuration and module dependencies management.
• Included docker-compose.yaml and other related provisioning files (access-control/sample.yaml, datasources/loki.yaml, notifiers/sample.yaml, plugins/sample.yaml, rules/rules.yml) for setting up the local testing environment, including services like Loki for logging.
• The .gitignore file has been updated to ignore unnecessary files and directories during development.

[cl-sonarqube-production]

Quality Gate passed

Issues
1 New issue
2 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube