Add ccip/changeset/internal

[connorwstein]

We want to reduce the public API surface of deployment/ccip and be more careful about the public API. To accomplish that:

• Moving the ccip/*.go files (ccipdeployment package) into ccip/changeset
• Move any easy files into ccip/changeset/internal
• Follow up: further pull logic into ccip/changeset/internal

At that point ccip/changeset and ccip/view represent the public API and internal holds details. This ensures that the integration-tests and chainlink-deployments modules don't import stuff we don't want them to.

[github-actions]

AER Report: CI Core

aer_workflow , commit , Detect Changes , Scheduled Run Frequency , Clean Go Tidy & Generate , Find New Flaky Tests In Chainlink Project / Get Tests To Run , lint , Core Tests (go_core_tests) , Core Tests (go_core_tests_integration) , Core Tests (go_core_ccip_deployment_tests) , Core Tests (go_core_race_tests) , Core Tests (go_core_fuzz) , Find New Flaky Tests In Deployment Project / Get Tests To Run , Find New Flaky Tests In Chainlink Project / Run Tests , Find New Flaky Tests In Chainlink Project / Report , Find New Flaky Tests In Deployment Project / Run Tests (github.com/smartcontractkit/chainlink/deployment/ccip/changeset, ubuntu-latest) , Flakey Test Detection , SonarQube Scan , Find New Flaky Tests In Deployment Project / Report

1. No space left on device:[Run tests with flakeguard]

Source of Error:

Run tests with flakeguard	2024-11-20T17:03:03.0025257Z github.com/uber/jaeger-client-go/thrift-gen/baggage: write /tmp/go-build4103662097/b1718/vet.cfg: no space left on device
Run tests with flakeguard	2024-11-20T17:03:03.0083925Z /usr/bin/ld: final link failed: No space left on device
Run tests with flakeguard	2024-11-20T17:03:03.0084447Z collect2: error: ld returned 1 exit status

Why: The error indicates that the device ran out of disk space, preventing the build process from writing necessary files and completing the linking stage.

Suggested fix: Ensure that there is sufficient disk space available on the device before running the tests. Clean up unnecessary files or increase the disk space allocation.

2. Running gcc failed: exit status 1:[Run tests with flakeguard]

Source of Error:

Run tests with flakeguard	2024-11-20T17:03:03.0030289Z /opt/hostedtoolcache/go/1.23.3/x64/pkg/tool/linux_amd64/link: running gcc failed: exit status 1

Why: This error is a consequence of the "No space left on device" error. The gcc compiler failed to complete its task due to insufficient disk space.

Suggested fix: Resolve the disk space issue as suggested above. Once there is enough space, the gcc compiler should be able to run successfully.

3. Invalid character 'g' looking for beginning of value:[Run tests with flakeguard]

Source of Error:

Run tests with flakeguard	2024-11-20T17:03:03.0092488Z error: invalid character 'g' looking for beginning of value

Why: This error likely occurred because the JSON output from the test results was corrupted or incomplete, possibly due to the previous errors related to disk space.

Suggested fix: After resolving the disk space issue, ensure that the test output is correctly generated and properly formatted as JSON. Re-run the tests to verify.

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

[connorwstein]

Just took one file to use as an example. There is a lot more we can hide in internal