Move daoracle config into own package

[ogtownsend]

• Referencing the oracle types as toml.OPStack, toml.Arbitrum looked and felt a little odd
• Creates a new package daoracle and moves the DA oracle config over so we can now reference them as daoracle.OPStack, etc

[github-actions]

Below is an analysis created by an LLM. Be mindful of hallucinations and verify accuracy.

WF: CI Core#8b4686e

Error 1: Test Failures in Go Core Tests

Source of Error:

Core Tests (go_core_tests)	Run tests	2024-10-11T22:50:08.0582639Z Encountered test failures.
Core Tests (go_core_tests)	Run tests	2024-10-11T22:50:08.0586109Z go_core_tests exiting with code 1
Core Tests (go_core_tests)	Run tests	2024-10-11T22:50:08.0604170Z ##[error]Process completed with exit code 1.

Why:
The error logs indicate that the Go core tests encountered failures, which caused the test script to exit with code 1. This exit code conventionally signifies an error state, typically used to indicate that a program has encountered an abnormal condition that prevented it from completing successfully.

Suggested Fix:
Review the specific test cases that failed, as indicated in the logs. Analyze the failure messages and stack traces to identify the root cause of each failure. Modify the test cases or the underlying application code to address these issues. Ensure that all dependencies and environment configurations are correctly set up for the tests to run successfully.

Error 2: API Server Not Ready

Source of Error:

Core Tests (go_core_tests)	Print Filtered Test Results	2024-10-11T22:50:09.2164807Z API server not ready yet (attempt 1): exit status 7
...
Core Tests (go_core_tests)	Print Filtered Test Results	2024-10-11T22:50:09.2182686Z API server not ready yet (attempt 30): exit status 7

Why:
The logs repeatedly show that the API server was not ready, with multiple attempts (up to 30) resulting in an "exit status 7". This status typically indicates that the server could not start properly, possibly due to misconfiguration, unmet dependencies, or conflicting resources (e.g., port already in use).

Suggested Fix:
Ensure that the API server configuration is correct, including the specified port, which should be free and not used by any other processes. Check the server logs for more detailed error messages that might indicate why the server failed to start. Adjust the configuration as necessary and ensure all required services and resources are available before starting the tests.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube