feat: configure automated changelog generation

[huynguyen-hl]

Description

This PR introduces the Create Changelog and Release workflows.

When a commit is pushed to a release/* branch (e.g., release/1.0.0, release/1.0.1, etc.), the create-changelog.yml workflow is triggered to generate or update the CHANGELOG.md file and create a corresponding PR.

The create-changelog.yml workflow utilizes the googleapis/release-please-action@v4 library to identify the changes made between the previous version and the current version, then generates or updates the CHANGELOG.md file accordingly.

Once the changelog PR is merged into the release branch, the release preparation is considered complete. At this point, the release branch can be merged into the main branch. This action triggers the release.yml workflow, which generates a new tag and creates a corresponding GitHub release. With these steps, the release process is finalized.

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build
• 🔁 CI
• 📦 Chore (Release)
• ⏩ Revert

Related Tickets & Documents

https://github.com/gs-gs/fa-ag-trace/issues/848

Mobile & Desktop Screenshots/Recordings

• The workflow is triggered after a commit is merged into the release/* branch:

• A PR is created by the create-changelog.yml workflow:

• Files changed:

---

After the release is merged into the main branch:

A tag is automatically created by the release.yml workflow, and its value corresponds to the version defined in the version.json file:

A GitHub release is automatically created once the tag is successfully generated. The release notes for this step are automatically generated by the create-changelog.yml workflow

Added tests?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help

Added to documentation?

• 📜 README.md
• 📕 storybook
• 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

[github-actions]

Coverage report

Caution

Coverage does not meet threshold
Statements coverage not met for global: expected <=25 not covered statements, but got 0

St.❔	Category	Percentage	Covered / Total
🟢	Statements	100%	0/0
🟢	Branches	100%	0/0
🟢	Functions	100%	0/0
🟢	Lines	100%	0/0

Test suite run success

0 tests passing in 0 suite.

Report generated by 🧪jest coverage report action from 31c45e3