[DEVPLAT-6523] feat: trigger release for dependency bumps

[Neurostep]

Description

The dependency upgrades from DEVPLAT-6523 were merged in #164 as chore: commits. Under our angular semantic-release preset (.releaserc.yml), chore: commits do not trigger a release, so no new version was cut after the merge.

main is protected, so the existing commit history can't be rewritten. This PR instead adds a single empty feat: commit, which provides a release-triggering message. Once merged, running the Release workflow will cut v1.49.0 (minor bump), regenerate the changelog, and bump the version files.

No code changes — the commit is intentionally empty.

Testing considerations

• After merge, trigger the Release workflow (workflow_dispatch) and verify commit-analyzer resolves a minor release and v1.49.0 is tagged/published.

Checklist

• Prefixed the PR title with the JIRA ticket code
• Performed simple, atomic commits with good commit messages
• Verified that the commit history is linear and commits are squashed as necessary
• Thoroughly tested the changes in development and/or staging
• Updated the README.md as necessary

Related links

• #164
• DEVPLAT-6523

---

Note

Low Risk
No runtime or source changes; only release metadata and versioning are affected when the Release workflow runs.

Overview
Adds an empty commit whose message is feat: so semantic-release (angular preset in .releaserc.yml) will treat main as releasable after dependency bumps landed only as chore: commits in #164.

There is no application or library code change in the diff. The intended follow-up is running the Release workflow to publish v1.49.0 (minor), refresh CHANGELOG.md, and update pkg/version (currently 1.48.0).

^{Reviewed by Cursor Bugbot for commit c5c86df. Bugbot is set up for automated code reviews on this repo. Configure here.}