[TT-1046] Add Chainlink node test config as TOML

[Tofel]

What was done?

• we can leverage existing TOML files that configure tests to pass CL node config
• it supports chain-specific configuration, where configuration is selected based on chain id; if no match is found, then default is used
• functional options used for programmatically configuring chainlink node TOML configuration were removed (so that we don't have to think about precedence of options vs TOML and about effectively communicating to the user which ones were used); functional options for CLNode were left untouched
• because OTEL tracing required unique ids for each node that id is generated programmatically, when we detect that tracing is enabled
• removed methods from builder that were not needed any more and renamed another one to better reflect what they do

⚠️ Disclaimer ⚠️
Chainlink nodes funding has been increased for some tests, due to default GasEstimator settings that's higher than it was in the past. If that's an issue, please let me know!

[jmank88]

Do we have to nest this TOML? Depending on the TOML lib, I think it would be possible to use a type for this field which defers parsing (like json.RawMessage), so that we could handle it as dynamic TOML instead of an opaque string.

[Tofel]

I do like this idea, but my only doubt is that it will work differently than it does now in CCIP and idk if it's worth diverting.

[cl-sonarqube-production]

Quality Gate passed

Issues
1 New issue
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