[bulk] Update release-automation + validation callers

[camara-release-automation]

Update release-automation + validation callers for SimpleEdgeDiscovery

TL;DR: This PR updates the release automation and CAMARA Validation workflows in SimpleEdgeDiscovery to the latest version from camaraproject/tooling (@v1-rc / @v1-rc).

Reminder: what release automation does

The release automation workflow enables slash commands on Release Issues to manage your release lifecycle. Post these as comments on the Release Issue:

• /create-snapshot — create a snapshot branch (updates versions, changelog entries, and release metadata automatically)
• /discard-snapshot <reason> — discard a snapshot and return to planned state
• /delete-draft — delete a draft release
• /publish-release --confirm rX.Y — publish the release

Refs applied

Caller	Pinned to
.github/workflows/release-automation.yml	@v1-rc
.github/workflows/camara-validation.yml	@v1-rc

Changes

 .github/workflows/camara-validation.yml  | 2 +-
 .github/workflows/release-automation.yml | 2 +-
 CHANGELOG.md                             | 3 +++
 CHANGELOG/README.md                      | 6 ++++++
 4 files changed, 11 insertions(+), 2 deletions(-)

See the PR's Files changed tab for the full diff.

What to do next

1. Review the changes above
2. Merge this PR
3. Trigger the workflow manually once to make sure all changes are applied:
   • Go to Actions → Release Automation → Run workflow

Documentation

📖 Release Management Documentation
📖 Release Lifecycle
📖 The release-plan.yaml File

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	4		0	0.01s
✅ API	spectral	1		0	1.56s
✅ GHERKIN	gherkin-lint	1		0	0.35s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	secretlint	yes		no	0.64s
✅ YAML	yamllint	1		0	0.45s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[hdamker]

@Kevsy resetting the workflows from the head of development branch to the tested v1-rc tag (as the r2.3 is done) and preparing the CHANGELOG structure for the new release cycle.