fix(cd): switching master deployment to release on production

[ChronosSF]

Closes #

Checklist:

• check topic's TOC/menu and paragraph headings
• Include TOC topic labels in the topic content when it has a valuable update, is new, or is considered preview / beta
• link to other topics using ../relative/path.md
• at the References section at the end of the topic add links to topics, samples, etc
• reference API documentation instead of adding a section with API

• use valid component names - [Data] Grid, IgxSelectComponent, <igx-combo>
• use spell checker tool (VS Code, Grammarly, Microsoft Editor)
• add inline code blocks for the names of classes / tags / properties
• add language descriptor for the code blocks
• check if links function by running the check-api/mdx npm commands
• check if sample is working and fully visible in the topic
• check if sample is working and fully visible in the StackBlitz
• check if code blocks match the code in StackBlitz demo

• follow SEO guidelines to fill topic's metadata (SEO guidelines)

• do not resolve requested changes (leave that to the reviewer)

[Copilot]

Pull request overview

Updates the reusable CD deploy workflow to treat builds targeting master as production builds, aligning the build command and downstream deploy payload with production deployment.

Changes:

• Switch BUILD_TYPE from always-staging to production when inputs.target_ref targets master.

---

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