Move to GitFlow strategy [ci patch inc]

[HyperWinX]

Update workflows to comply with GitFlow strategy.

[mentatbot]

I'm getting to work. See my steps and track my cost here.

• Wake on any new activity.
  _{I always see new activity while actively working. When paused, I'll only respond when tagged unless this box is checked.}

[mentatbot]

I've reviewed the changes to move to GitFlow strategy. The workflow updates look clean and well-structured, with several improvements:

• Simplified the CI/CD pipeline by focusing on PR-based workflow
• Removed potentially dangerous force pushes
• Made versioning more explicit with clear commit message tags
• Improved job organization and naming

This is a good move toward a more controlled release process, which aligns well with GitFlow principles. The changes look good to merge.

One note: There appears to be a small issue in the versioning-minor-increment job - the condition is set to if: "!contains(github.event.head_commit.message, '[ci minor inc]')" which would trigger for commits without the tag. I believe this should be changed to use a positive condition like the patch job does.