Unify tokens usage in repos

[lmolotii]

Summary

• Switch Deploy Prod (publish-tagged.yml) from secrets.CROSS_REPO_PAT to secrets.CROSS_REPO_PAT_V2 for the Lambda-Recipes workflow dispatch.
• Align comments in Deploy Dev and Deploy Prod so they document only CROSS_REPO_PAT_V2.
• Ensure every cross-repo auth path in this repository uses a single Actions secret.

Motivation

Deploy Dev already used CROSS_REPO_PAT_V2 for both the wrangleworks.github.io checkout/push and the Lambda-Recipes dispatch. Deploy Prod still referenced the legacy CROSS_REPO_PAT secret, which risked silent divergence (or failure) if only V2 is maintained.

Behavior / API impact

• No product code changes.
• After merge, Deploy Prod requires CROSS_REPO_PAT_V2 to have Actions: Read and write on wrangleworks/Lambda-Recipes (same token already used by Deploy Dev for github.io Contents R/W and Lambda-Recipes dispatch).