refactor: remove redundant options param from copyConfigKeyEntry

[craigmichaelmartin]

WHY are these changes introduced?

copyConfigKeyEntry accepted both a context: BuildContext (nested inside the config object) and a separate options: { stdout } parameter. Since context.options already carries stdout, the second parameter was redundant — every caller was passing context.options as the second argument anyway. The inconsistency was highlighted by a recent outputDebug call that reached for context.options.stdout instead of options.stdout.

Follow-up to #7142.

WHAT is this pull request doing?

• Remove the options second parameter from copyConfigKeyEntry
• Destructure stdout from context.options inside the function
• Update the single call site in include-assets-step.ts
• Update the test helper makeContext to include stdout in options, and remove the now-unnecessary second argument from all copyConfigKeyEntry test calls

How to test your changes?

Run the existing tests — no behaviour changes, pure refactor.

Measuring impact

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes

🤖 Generated with Claude Code

[github-actions]

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run pnpm changeset add to track your changes and include them in the next release CHANGELOG.

Caution

DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release.