Move to GitFlow strategy [ci patch inc]

[HyperWinX]

Update workflows to comply with GitFlow strategy rules.

[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 your GitFlow implementation PR and it looks good! Here's what I like about the changes:

1. Clear separation of workflows:

   • Feature branch testing happens automatically on push
   • PR testing and versioning happens on PRs to master

2. Explicit versioning:

   • Using [ci patch inc] and [ci minor inc] tags makes versioning intentional
   • Removed automatic versioning that could be triggered unintentionally

3. Simplified workflow:

   • Removed complex branch manipulation and force pushes
   • Cleaner commit messages for version increments

One question: I noticed the versioning-patch-increment job no longer depends on the testing job. Is this intentional? This would allow patch version increments without tests passing first. If you're relying on PR checks to ensure tests pass before merging, that might be acceptable, but wanted to check.

Overall, this looks like a good move toward a more maintainable GitFlow workflow!