Document Pyoxy Release Schedule

I'm interested in using Pyoxy as my go-to way of setting up all the python interpreters I need. I would love to use the same setup for my Linux servers, as I use for my macOS workstation and downloading a single file and renaming it really fits the bill.

I might be interested in the PEX alternative you mention in [your blog post](https://gregoryszorc.com/blog/2022/05/10/announcing-the-pyoxy-python-runner/) down the line as well, but for now I just really like the thought of having my interpreter be a single file on all of my hosts.

Long-story short: I noticed that Pyoxy didn't get a new release after 0.2.0, even though Pyoxidizer and Python-Build-Standalone did. Since I generally like to use the latest patch releases of Python I was wondering what the plans were with regards to releases. Could this be done in some sort of CI job that would run every time Python creates a new release, or do you need to do a lot of manual work each time?

Alternatively, is it possible to chain these projects together, so that if one gets a new release, the others do as well? My main concern is that I switch everything to Pyoxy and then end up having outdated Python releases running on my infrastructure.

Thanks for all your work!

Review Pyoxy's release history around version 0.2.0 alongside PyOxidizer and Python-Build-Standalone releases, and read the linked Pyoxy announcement. Determine whether a release schedule, CI-triggered releases, or chained project releases is the intended scope; done should include an agreed approach that keeps supported Python patch releases current.

Written by the indexing model from the issue text.