Beholder config: bump EmitterExportTimeout to 30s (OTel default)

[pkcll]

Beholder config: bump EmitterExportTimeout to 30s (OTel default)

[github-actions]

AER Report: CI Core

aer_workflow , commit , Detect Changes , Scheduled Run Frequency , Clean Go Tidy & Generate , Flakeguard Root Project / Get Tests To Run , lint , Core Tests (go_core_tests) , Core Tests (go_core_tests_integration) , Flakeguard Deployment Project , Core Tests (go_core_ccip_deployment_tests) , Core Tests (go_core_race_tests) , Core Tests (go_core_fuzz) , Flakeguard Root Project / Run Tests (github.com/smartcontractkit/chainlink/v2/core/services/chainlink, ubuntu-latest) , Flakeguard Root Project / Report , Flakey Test Detection , SonarQube Scan

1. Test failures encountered: [Run tests]

Source of Error:

Run tests	2024-11-25T14:30:34.6321491Z Encountered test failures.
Run tests	2024-11-25T14:30:34.6331694Z go_core_tests exiting with code 1
Run tests	2024-11-25T14:30:34.6341960Z ##[error]Process completed with exit code 1.

Why: The error indicates that some tests in the go_core_tests suite failed, causing the process to exit with a non-zero status code (1), which is a standard indication of failure in Unix-like systems.

Suggested fix: Review the test output logs to identify which specific tests failed and address the underlying issues in the code or test cases. Ensure all dependencies and configurations are correctly set up.

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

[github-actions]

I see you added a changeset file but it does not contain a tag. Please edit the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

🎖️ No JIRA issue number found in: PR title, commit message, or branch name. Please include the issue ID in one of these.