[🚀 Feature]: Make a separate patch release for the patch release artifacts

[chenrui333]

Feature and motivation

From the downstream packaging perspective, we are use a generic livecheck to consume the version information, but it would be disrupted when the version info is not consistent between the tag and the release artifact, hence it would be good to also create releases for the patches releases. Let me know if that makes sense.

relates to:

• selenium-server 4.24.0 Homebrew/homebrew-core#182960
• [🐛 Bug]: missing selenium-server-4.9.1.jar? #12074

[github-actions]

@chenrui333, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[diemol]

Unfortunately, we cannot commit to this due to the team's small size.

We are trying to simplify and automate the release process, and we might revisit this after we are done with that.