Update S3_0 msys2 environment
We are likely to update msys2 environment of S3_0 during its lifetime. Most probable around the time 3.1.0-beta1 gets released, and with the same environment version.
One thing that we may need to port to S3_0 before we can update the msys2 environment is localization fix #44047.
Attached patch makes it possible to use msys2-220309 with S3_0. Not meant for committing, but just available for developers who want to use newer environment.
As noted in #44286, msys2 upstream will bump their minimum requirement to Windows-8.1, and we can't take that to S3_0. So any update of S3_0 msys2 update needs to be to a version earlier than their req bump. At this point I assume it to mean that we will do the update to 3.0.3 (can't leave later, we don't want to do it unnecessarily early)
Likely we have two iterations of this during the 3.0.3 cycle. As soon as 3.0.2 has been released, we can set S3_0 to use what ever msys2 environment we have for S3_1/master at the time. Then we make the final msys2 environment later during the cycle.
Reply To cazfi
As soon as 3.0.2 has been released, we can set S3_0 to use what ever msys2 environment we have for S3_1/master at the time.
Update for S3_1/master coming in #43947 - even if that's not ready by 3.0.2 release, we may want to wait for it for S3_0 too.