Custom port exposure, API credentials override in outputs

[skudasov]

• Add custom port exposure in TOML
• Return default user/password credentials in outputs, so we can connect to any node by overriding TOML params
• Change clclient.New signature

---

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

Why

The changes enhance the flexibility and security of Chainlink nodes in test environments by allowing custom port configurations and setting default API credentials for node authentication. These adjustments facilitate more dynamic testing setups and secure connections to Chainlink nodes.

What

• book/src/SUMMARY.md
  • Changed the title from "Components Persistence" to "Exposing Components" for clarity on the section's content.
• book/src/framework/components/chainlink/node.md and nodeset.md
  • Added documentation for new custom_ports, api_auth_user, and api_auth_password configurations, enabling custom port mappings and default API credentials for Chainlink nodes.
• book/src/framework/components/external.md
  • Included new fields api_auth_user and api_auth_password in the example TOML configuration to highlight the capability to set default API credentials for external components.
• book/src/framework/components/state.md
  • Title changed to better reflect the content on exposing component data and ports.
  • Added a new section on custom ports, explaining how to configure them for nodes.
• book/src/framework/test_configuration_overrides.md
  • Added guidance on overriding component configurations, emphasizing the hierarchy and application of overrides.
• framework/.changeset/v0.2.4.md
  • Documented the addition of custom port exposure and default API credentials in output configurations, and a change in the clclient.New function signature.
• framework/clclient/client.go
  • Updated the NewChainlinkClient function to utilize the new output fields for API credentials, removing hardcoded defaults in favor of configurable options.
• framework/components/clnode/clnode.go
  • Implemented the handling of custom_ports in node configurations and included default API credentials (api_auth_user, api_auth_password) in the node output for secure authentication.
• framework/components/simple_node_set/node_set.go
  • Modified node set setup to accommodate custom port configurations, ensuring each node in a set can specify its own set of ports.
• framework/examples/myproject/README.md
  • Added a new "Level 0" section to the Project Maturity Model, outlining initial planning and integration considerations for testing.
• Various test files in framework/examples/myproject/
  • Replaced NewCLDefaultClients with the updated New function to align with changes in client initialization, reflecting the shift to configurable API credentials.

[cl-sonarqube-production]

Quality Gate passed

Issues
2 New issues
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube