FINERACT-2158: Add workflow to enforce PR title convention

[DeathGun44]

Description

Adds a lightweight GitHub Action to automatically enforce the project's PR title convention (e.g. FINERACT-123: Description). This helps ensure cleaner changelogs and release notes.

The workflow uses a regex check (^FINERACT-[0-9]+:) and fails fast if the format is incorrect.

FINERACT-2158

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

• Write the commit message as per our guidelines
• Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
• Create/update unit or integration tests for verifying the changes made. (Verified workflow execution on fork)
• Follow our coding conventions.
• Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
• This PR must not be a "code dump"(https://cwiki.apache.org/confluence/display/FINERACT/Pull+Request+Size+Limit). Large changes can be made in a branch, with assistance. Ask for help on the developer mailing list.

[Aman-Mittal]

LGTM

[IOhacker]

LGTM

[IOhacker]

@DeathGun44 I will add Adam Monsen's comments here:

Future improvement idea: ensure the referenced JIRA ticket exists, e.g.ISSUE_ID=2158
HTTP_CODE=$(curl -I -s -o /dev/null --write-out "%{http_code}" https://issues.apache.org/jira/browse/FINERACT-$ISSUE_ID)
[[ $HTTP_CODE -eq 200 ]]

[meonkeys]

Thanks @IOhacker ! I added them to FINERACT-2158 as well.

[IOhacker]

@meonkeys Thank you!