ccip: use unknown address type.

[winder]

Update ccip capability to use the unknown address type introduced with smartcontractkit/chainlink-ccip#248

[github-actions]

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in 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.

[github-actions]

AER Report: CI Core

aer_workflow , commit , Detect Changes , Clean Go Tidy & Generate , lint , Core Tests (go_core_tests) , Core Tests (go_core_ccip_deployment_tests) , Core Tests (go_core_race_tests) , Core Tests (go_core_fuzz) , SonarQube Scan

1. Process completed with exit code 1: Core Tests (go_core_ccip_deployment_tests)

Source of Error:

Print Filtered Test Results	2024-10-21T15:16:33.8605453Z ##[error]Process completed with exit code 1.

Why: The error indicates that the process running the core tests for the go_core_ccip_deployment_tests job has failed, resulting in an exit code of 1. This is a generic error code indicating that the process did not complete successfully.

Suggested fix: Review the specific test cases and logs preceding this error to identify the root cause. Ensure all dependencies are correctly installed and configurations are properly set.

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

[cl-sonarqube-production]

Quality Gate passed

Issues
3 New issues
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube