fix: ensure package name is encoded

[paustint]

Ensure that an outbound package name is encoded properly to avoid "No package.xml found"

[Copilot]

Pull request overview

This PR addresses failures when deploying metadata into an existing outbound Change Set by ensuring the outbound package/change set name is URI-encoded before being used downstream (preventing Salesforce-side “No package.xml found” scenarios when the name contains special characters).

Changes:

• Rename the onDeploy callback’s first parameter for clarity (changesetPackage → packageName).
• Encode the selected packageName via encodeURIComponent before passing it into the deploy flow.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
libs/features/deploy/src/add-to-changeset/AddToChangesetConfigModal.tsx	Clarifies the deploy callback parameter name to better reflect what’s passed.
libs/features/deploy/src/add-to-changeset/AddToChangeset.tsx	Encodes the outbound package/change set name before triggering the deploy workflow.

---

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