chore(vdev): add vdev release command

[pront]

Summary

Vector configuration

How did you test this PR?

Will try to release after this is merged.

Change Type

• Bug fix
• New feature
• Non-functional (chore, refactoring, docs)
• Performance

Is this a breaking change?

• Yes
• No

Does this PR include user facing changes?

• Yes. Please add a changelog fragment based on our guidelines.
• No. A maintainer will apply the no-changelog label to this PR.

References

Notes

• Please read our Vector contributor resources.
• Do not hesitate to use @vectordotdev/vector to reach out to us regarding this PR.
• Some CI checks run only after we manually approve them.
  • We recommend adding a pre-push hook, please see this template.
  • Alternatively, we recommend running the following locally before pushing to the remote branch:
    • make fmt
    • make check-clippy (if there are failures it's possible some of them can be fixed with make clippy-fix)
    • make test
• After a review is requested, please avoid force pushes to help us review incrementally.
  • Feel free to push as many commits as you want. They will be squashed into one before merging.
  • For example, you can run git merge origin master and git push.
• If this PR introduces changes Vector dependencies (modifies Cargo.lock), please
  run make build-licenses to regenerate the license inventory and commit the changes (if any). More details here.

[thomasqueirozb]

Does this push a commit directly to master? I don't think this is a good idea and I also don't think it will work since we have branch protection rules

[pront]

This is the simplest way. Only repo maintainers will ever use this script and they can push to master. I considered bumping locally, publishing, and making a workflow commit the new version. But I don't see why the latter is better really.

Alternative is to make a PR, update the version and then run this script to update the tag. You can think about it a bit more if you want.