feat: add customizable git messages

[bayssmekanique]

Issue

In the current implementation the git messages are hard coded and mostly sane defaults, but many CI/CD workflows require specific formatting or keywords in commit messages (for linting or job triggering). An example would be conventional commit linted system where a required <type> and optional [scope] prefix on commit messages could cause issues with deployment.

Suggested Resolution

The best solution I could come up with is to simply allow overriding of commit messages in the configuration file. This could get a bit heavy as there are a few different types of commit messages currently used, and several have multiple messages depending on the CRUD operation being performed, but this would be the most flexible solution.

[hunvreus]

2 things:

• I could make the commit messages configurable in the .pages.yml file, that shouldn't be too complicated.
• I would also like to let users potentially override the default message when making a change via the interface. This is probably something I'll enable when I add a delay on actions (e.g. you have 5 seconds to cancel a save/delete before it effectively happen).