What does this PR do?

This PR introduces a new CI check that validates Pull Request titles against conventional commit message standards. This ensures that when PRs are squash-merged into the main branch, the resulting commit messages consistently follow the desired type(scope): description format, which is crucial for automated changelog generation and commit history clarity.

The check uses amannn/action-semantic-pull-request@v5 and enforces:

• Allowed conventional commit types (e.g., feat, fix, chore).
• Optional scopes.
• A lowercase subject line.

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Chore (refactoring code, technical debt, workflow improvements)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (does not change functionality, e.g. code style improvements, linting)
• This change requires a documentation update

Mandatory Tasks

• Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.

Checklist

• I haven't read the contributing guide
• My code doesn't follow the style guidelines of this project (pnpm run format)
• I haven't commented my code, particularly in hard-to-understand areas
• I haven't checked if my PR needs changes to the documentation
• I haven't checked if my changes generate no new warnings (npm run lint)
• I haven't added tests that prove my fix is effective or that my feature works
• I haven't checked if new and existing unit tests pass locally with my changes