fix: concurrency fixes for release-drafter and deploy-site workflows

[vishalvivekm]

Notes for Reviewers

This PR assignes different concurrency groups to release-drafter and deploy workflows to ensure they can run independently, at the same time.

Release Drafter:

• ignore changes made to .github or archive/ (cloud releases) folders.
• only one workflow runs at a time, latest one cancels previous runs

Pages deployment:

• only one workflow runs at a time; latest incoming run cancels any running workflow. Ensures we always deploy the latest changes rather than outdated code.

Behaviour:

Workflow A arrives → finds nothing in its concurrency group → starts running
Workflow B arrives → finds job A running in its concurrency group → kills A → starts running

Signed commits

• Yes, I signed my commits.

[netlify]

✅ Deploy Preview for bejewelled-pegasus-b0ce81 ready!

Name	Link
🔨 Latest commit	3f05a48
🔍 Latest deploy log	https://app.netlify.com/projects/bejewelled-pegasus-b0ce81/deploys/6867e6b51d8f880008408a81
😎 Deploy Preview	https://deploy-preview-629--bejewelled-pegasus-b0ce81.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[leecalcote]

Do we need the release-drafter workflow? If "no", please proof the the release notes included in the Cloud releases and the Kanvas releases are sourced elsewhere,