feat: improve changelog creation and auto label pr's

[Sim-sat]

Description

What problem does this PR solve?
What problem does this PR solve?
The current changelogs are difficult to read because they lack categorization and include technical debt or chores that provide no value to end-users.

How did you implement the solution?
I have improved the native GitHub release auto-generation by adding a release.yml configuration and a workflow that automatically labels PRs based on their titles and selected checkboxes. This automates organized changelogs without requiring manual intervention. I also improved the pr validation to make it a little bit less strict and to post a comment to make it easier to understand errors..

Suggested Label Updates

@CodeWithCJ I suggest creating the following labels to optimize categorization:

• ​skip-changelog (To hide internal chores/refactors from users)
• ​mobile
• ​frontend
• ​backend
• ​security
• ​refactor
  ​
  The mobile, frontend, and backend labels would only be used for making it easier for us to keep an overview, because github doesn't support nesting the categories in the changelog template.

Linked Issue: #

How to Test

1. Check out this branch and run ...
2. Navigate to...
3. Verify that...

PR Type

• Issue (bug fix)
• New Feature
• Refactor
• Documentation

Checklist

All PRs:

• [MANDATORY - ALL] Integrity & License: I certify this is my own work, free of malicious code, and I agree to the License terms.

New features only:

• [MANDATORY for new feature] Alignment: I have raised a GitHub issue and it was reviewed/approved by maintainers or it was approved on Discord.

Frontend changes (SparkyFitnessFrontend/ or src/):

• [MANDATORY for Frontend changes] Quality: I have run pnpm run validate and it passes.
• [MANDATORY for Frontend changes] Translations: I have only updated the English (en) translation file.

Backend changes (SparkyFitnessServer/):

• [MANDATORY for Backend changes] Code Quality: I have run typecheck, lint, and tests. New files use TypeScript, new endpoints have Zod schemas, and new endpoints include tests.
• [MANDATORY for Backend changes] Database Security: I have updated rls_policies.sql for any new user-specific tables.

UI changes (components, screens, pages):

• [MANDATORY for UI changes] Screenshots: I have attached Before/After screenshots below.

Screenshots

Notes for Reviewers

Optional — use this for anything that doesn't fit above: known tradeoffs, areas you'd like specific feedback on, qustions you have or context that helps reviewers.

[gemini-code-assist]

Code Review

This pull request introduces a .github/release.yml configuration file to automate the generation of release notes. The review feedback suggests expanding the exclusion list to include non-user-facing labels such as refactor and backend, and adding specific categories for Security, Mobile, and Frontend to better organize the changelog output.

[Sim-sat]

/gemini review

[gemini-code-assist]

Code Review

This pull request updates the pull request template to include a mobile changes section and standardizes the linked issue format. It also introduces a configuration for automated release changelogs. Feedback points out that the PR description mentions automation workflows that are not included in the changes. Additionally, suggestions were made to add quality and translation checkboxes to the mobile section of the template and to exclude 'chore' and 'dependencies' labels from the release changelog.

[CodeWithCJ]

Is this still in draft?

[Sim-sat]

Is this still in draft?

It's working, I tested it on my fork, but I wanted to wait until you created the labels. I don't know what happens when they dont exist

[CodeWithCJ]

My bad. I didn't read the PR completely. Currently on mobile. I'm afraid I can do this only next weekend.

[Sim-sat]

Yeah don't worry it's not that important. Just tell me that when you add them

My bad. I didn't read the PR completely. Currently on mobile. I'm afraid I can do this only next weekend.