feat: Update github actions to handle orchestration spec updates

[BrigittaK307]

Context

Closes SAP/ai-sdk-js-backlog#478

What this PR does and why it is needed

Modified cron job to handle orchestration spec updates, too.
The changes should be aligned with what the Java team implemented.

[hyperspace-insights]

Summary

The following content is AI-generated and provides a summary of the pull request:

⚠️ Warnings:

• Could not get access to repository SAP/ai-sdk-js-backlog to retrieve Issue 478. Status: 404 - UnknownObjectException

---

feat: Update GitHub Actions to handle orchestration spec updates

New Features

✨ Enhanced the spec file update cron job to automatically handle orchestration service specification updates alongside existing AI API, document grounding, and prompt registry updates. The workflow now dynamically fetches orchestration versions and triggers appropriate spec updates.

Changes

• .github/workflows/spec-update-cron.yaml:
  • Added workflow_dispatch trigger for manual workflow execution
  • Refactored from individual jobs to a single matrix-based job (update-all-specs) that processes multiple spec files in parallel
  • Added orchestration to the matrix of spec files to be updated
  • Implemented dynamic version fetching for orchestration from the MLF GitOps repository
  • Added logic to construct appropriate branch names for orchestration updates (removing hotfix suffixes and using rel- prefix)
  • Integrated Slack failure notifications for better visibility when spec updates fail
  • Streamlined workflow by consolidating all spec updates into a unified process with conditional logic

GitHub Issues

• SAP/ai-sdk-js-backlog#478: Regenerate AI Core client with a default base path

---

• 🔄 Regenerate and Update Summary
• ✏️ Insert as PR Description (deletes this comment)
• 🗑️ Delete comment

PR Bot Information

Version: 1.17.61 | 📖 Documentation | 🚨 Create Incident | 💬 Feedback

• Event Trigger: issue_comment.edited
• Output Template: Default Template
• Summary Prompt: Default Prompt
• LLM: anthropic--claude-4.5-sonnet
• Correlation ID: f6c216e0-0ccd-11f1-8be1-29f9d3a74cb0
• GithubContextProvider: chore: Regenerate AI Core client with a default base path #478

[davidkna-sap]

Please match this logic instead (but maybe use yq):
https://github.com/SAP/ai-sdk-java/blob/main/.github/workflows/weekly-spec-update.yaml#L27-L50

This should match the actual service version, also not every tag has a release.

[davidkna-sap]

I feel like it should error in this case so it can send a slack notification.

[davidkna-sap]

[pp]

Suggested change

	-H "Accept: application/vnd.github.v3.raw" | grep 'version:' | awk '{print $2}')
	-H "Accept: application/vnd.github.v3.raw" | yq -r .version)

[davidkna-sap]

[pp] Doesn't hut keeping this verbose:

Suggested change

	gh workflow run spec-update.yaml \
	--field file=${{ matrix.file }} \
	gh workflow run spec-update.yaml \
	--ref main \
	--field file=${{ matrix.file }} \

[davidkna-sap]

Please preserve the existing/commented RPT update script somewhere, either as a step like orchestration or here in 'Trigger spec update'.

TAG=$(git -c 'versionsort.suffix=-' ls-remote --tags --sort='v:refname' https://github.tools.sap/DL-COE/sap-rpt-1-public-content | tail --lines=1 | cut -f 2)