Automatically bump version during template update

[edmundmiller]

When a new Template gets released, the pipeline semver should match the tools semver bump.

So for example:

Template Update	Pipeline Version
2.10.0 => 3.0.0	3.16.0 => 4.0.0
3.0.0 => 3.1.0	3.16.1 => 3.17.0
3.0.0 => 3.0.1	3.16.1 => 3.16.2

We should automate this bumping during the PRs somehow and nudge the developers to cut a release if it's past 1.0.0

[mashehu]

Nope, because the template might not have breaking changes, so it would still be used in the same way as before. E.g. The big change with 3.0.0 was modularity, the TUI and the new pipelines subcommand. Nothing changed for the pipelines themselves.