chore(notask): standardize workflow names for monitoring consistency

[kb-typeform]

What

Standardize GitHub Actions workflow name: fields to follow the agreed convention:

• PR workflow: Pull Request (Consolidated)
• Deploy workflow: Deploy (Consolidated)

Why

Consistent workflow names are needed for:

• Datadog CI Visibility monitoring
• GitHub Actions usage dashboards
• Cross-repo pipeline duration comparisons

Changes

One-line name: field changes in workflow YAML files. No functional changes.

Related

Part of PLT-2547 CI Consolidation cleanup.

[pr-auditor]

✅ Security Analysis Results

Great news! No security issues found in this pull request.

Analysis Summary:

• 📁 Files reviewed: 2
• ✅ No security vulnerabilities detected

---

Security analysis powered by Claude Sonnet 4.6 via pr-auditor | Questions? Contact #dx-team or check out this page

[gitstream-cm]

This PR is missing a Jira ticket reference in the title or description.
Please add a Jira ticket reference to the title or description of this PR.

[gitstream-cm]

🥷 Code experts: pannago

pannago has most 👩‍💻 activity in the files.
pannago has most 🧠 knowledge in the files.

See details

.github/workflows/pull-request.yml

Activity based on git-commit:

	pannago
APR	137 additions & 0 deletions
MAR
FEB
JAN
DEC
NOV

Knowledge based on git-blame:
pannago: 100%

.github/workflows/release.yml

Activity based on git-commit:

	pannago
APR	80 additions & 0 deletions
MAR
FEB
JAN
DEC
NOV

Knowledge based on git-blame:
pannago: 100%

✨ Comment /gs review for LinearB AI review. Learn how to automate it here.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[typeform-ops-gha]

[BOT] Preview available with hash e5ab9859b5d0d386280e185809f37accf15be392 here.

[Bogdan-Zvyagintsev]

lgtm