Improve git commits and harmonize the contribution practices with artemiscloud/activemq-artemis-operator and the broker

[lavocatt]

On the operator there is a constraint so that every commit is linked to an issue (or to explicitly tell that there are no related issues):

• https://github.com/artemiscloud/activemq-artemis-operator/blob/main/.github/workflows/merge-rules.yml

On the broker, there are constraints on the actual commit format:

• https://activemq.apache.org/components/artemis/documentation/hacking-guide/#commit-messages
• https://activemq.apache.org/components/artemis/documentation/hacking-guide/#commitMessageDetails

I think that these are two good practices that we should also do for the provisioning plugin.

A better set of git commits lead to a better upstream developer experience. For external contributors, a history containing enough information is key to understand the evolution of the code base. For us it will help solving the future bugs we will have to fix, mainly for the same reasons.

What's your opinion on the subject?