feat: add changeset tx type

[anirudhwarrier]

DEVSVCS-3460

This pull request introduces support for a new "changeset" transaction type across several CLI commands, enabling users to generate YAML changeset files for key linking, unlinking, and secrets management workflows. It also consolidates transaction type flag handling and adds utility functions for writing changeset files. The most significant changes are grouped below:

Support for "changeset" transaction type in CLI commands:

• Added a new Changeset transaction type to the TxType enum and transaction execution logic in cmd/client/tx.go, allowing commands to handle changeset workflows. [1] [2] [3]
• Updated link_key, unlink_key, and secrets commands to support the new transaction type, generating and writing YAML changeset files when selected. This includes logic to build the changeset payloads and write them to the appropriate directory. [1] [2] [3] [4] [5]

Flag handling and codebase consistency:

• Replaced AddRawTxFlag with a more general AddTxnTypeFlags in all affected commands, making transaction type selection more flexible and consistent. [1] [2] [3] [4]

Utility and integration improvements:

• Added a utility function WriteChangesetFile in cmd/common/utils.go to handle YAML marshaling and file writing for changeset files.
• Updated imports and handler structs to support the new changeset logic and ensure correct dependencies are included throughout the codebase. [1] [2] [3] [4] [5] [6] [7]

Workflow registry integration:

• Refactored AllowlistRequest in workflow_registry_v2_client.go to return a TxOutput and support the new transaction type, enabling the allowlist operation to participate in the changeset workflow.

These changes collectively enable the CLI to support multi-stage, auditable changes via YAML changesets, improving workflow flexibility and external integration.

[Copilot]

Pull request overview

This PR introduces support for a new "changeset" transaction type, enabling users to generate YAML changeset files for key linking, unlinking, secrets management, and workflow operations instead of executing transactions directly on-chain. This facilitates multi-stage, auditable changes that can be consumed by external deployment tooling (CLD).

Key changes:

• Added Changeset transaction type alongside existing Regular, Raw, and Ledger types
• Implemented changeset generation logic across workflow commands (deploy, activate, pause, delete) and secrets operations
• Introduced CLD settings configuration for changeset file generation paths and MCMS parameters

Reviewed changes

Copilot reviewed 22 out of 23 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
internal/types/changeset.go	Defines new changeset file structures and operation types
internal/settings/workflow_settings.go	Adds CLD settings configuration structure for changeset paths and MCMS parameters
internal/settings/settings_load.go	Adds changeset flag and consolidates transaction type flag handling
internal/settings/settings_get.go	Adds MCMS config getter and updates owner validation logic for changeset type
go.mod	Updates dependencies including chainlink deployment packages required for changeset support
cmd/workflow/*/*.go	Implements changeset generation for workflow operations (deploy, pause, activate, delete)
cmd/secrets/*/*.go	Implements changeset generation for secrets operations (list, create, update, delete, execute)
cmd/common/utils.go	Adds utility function to write changeset YAML files
cmd/client/workflow_registry_v2_client.go	Refactors AllowlistRequest to return TxOutput supporting changeset type
cmd/client/tx.go	Adds changeset transaction type handling
cmd/client/client_factory.go	Adds changeset type detection in transaction factory
cmd/account/link_key/link_key.go	Implements changeset generation for key linking
cmd/account/unlink_key/unlink_key.go	Implements changeset generation for key unlinking

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The error from MarkHidden is silently discarded. Consider logging or handling this error, especially since hiding the flag is part of the feature's design (being non-public).

Suggested change

	_ = cmd.LocalFlags().MarkHidden(Flags.Changeset.Name) // hide changeset flag as this is not a public feature
	if err := cmd.LocalFlags().MarkHidden(Flags.Changeset.Name); err != nil { // hide changeset flag as this is not a public feature
	fmt.Fprintf(os.Stderr, "warning: failed to hide --%s flag: %v\n", Flags.Changeset.Name, err)
	}