Do not propose automated blog post for patch releases

[Bisaloo]

This makes some assumptions on git tag formatting but it seems reasonable to me. In particular, usethis, our recommend tool to create GitHub release, will generate tags with the following format v1.0.0.

This clashes with https://github.com/epiverse-trace/blueprints/pull/70 but matches @joshwlambert's request in #135:

However, I would appreciate if there was a general consensus that we do not publish posts for patch releases, and then major and minor can be handled on a case-by-case basis.

I believe critical fixes should not be released as patches and this will spare us some notification spam.

What do you think?

[netlify[bot]]

✅ Deploy Preview for tourmaline-marshmallow-241b40 ready!

Name	Link
🔨 Latest commit	b4f49192b6388a10771a9e39a1ce0cd40339f2f5
🔍 Latest deploy log	https://app.netlify.com/sites/tourmaline-marshmallow-241b40/deploys/66277e83a3be5e000756226c
😎 Deploy Preview	https://deploy-preview-237--tourmaline-marshmallow-241b40.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.