feat(deployment): add link token transfer changesets

[graham-chainlink]

Added a new changeset in shared package which transfer the link token.

JIRA: https://smartcontract-it.atlassian.net/browse/DPA-1314

[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) , Core Tests (go_core_ccip_deployment_tests) , Core Tests (go_core_race_tests) , Core Tests (go_core_fuzz) , Flakeguard Deployment Project / Get Tests To Run , Flakeguard Root Project / Run Tests , Flakeguard Root Project / Report , Flakeguard Deployment Project / Run Tests (github.com/smartcontractkit/chainlink/deployment/common/changeset, ubuntu-latest) , Flakeguard Deployment Project / Report , Flakey Test Detection , SonarQube Scan

1. Undefined function LoadLinkTokenState:

[Run tests] [2024-12-09T12:30:50.0739112Z] [common/changeset/transfer_link_token.go:57:21: undefined: LoadLinkTokenState]

Source of Error:

# github.com/smartcontractkit/chainlink/deployment/common/changeset
common/changeset/transfer_link_token.go:57:21: undefined: LoadLinkTokenState

Why: The error indicates that the function LoadLinkTokenState is being called in the file transfer_link_token.go but it is not defined or imported in the scope of this file.

Suggested fix: Ensure that LoadLinkTokenState is defined and properly imported in transfer_link_token.go. If it is defined in another package, make sure to import that package correctly. If it is missing, define the function in the appropriate location.

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

[connorwstein]

seems more like a QA function not really a configuration change?

[graham-chainlink]

That's true, we were planning to use this as a test and example for MCMS. Let me check with @RodrigoAD , see what he thinks

[RodrigoAD]

seems more like a QA function not really a configuration change?

Configuration is hard to define, in our case, any operation that is required to operate a protocol should be a changeset, as we need all the extra capabilities it provides, e.g. wrap the tx into a MCMS proposal. This operation falls in that category. Besides that, LINK is a simple contract that everyone understands, and will serve as a reference on how to implement changeset operations and proposals