Creating a Schedule for Development Cycles

[StandingPadAnimations]

First commented here, moving to its own issue for organization.

The idea is to take a page from Blender's book (with their BCON system) and create a general schedule for MCprep development cycles. While these wouldn't be hard deadlines, we can use this as a general indicator for seeing how far along we are with MCprep development, and plan releases accordingly.

After #446 is implemented, we could expand these time blocks (which again are merely suggestions), as MCprep wouldn't need as many releases (maybe 2 a year would be sufficient, but I digress).

Now why? In the past, MCprep development cycles would go on for long periods of time. In addition, we generally try to get every PR made pushed to the next release, even if said release is meant to come around the corner; this leads to unnecessary rushing. It makes sense, in my experience it's hard to tell people “actually, let's delay this for a little bit” (many of us have been in that boat 😅). A schedule system however would make it not only easier for us to tell people that we'll delay their PRs, it also gives them a general idea of the development timeline. Who knows, the extra time might mean more developed PRs in the long run?

What do y'all think?