When cutting an open-source WiredTiger release, there's one step to update the Python compatibility tests (i.e. test/suite/test_compat0[1-4].py) in order to extend the log version compatibility testing coverage for the newer release version. Right now it's a manual update step that requires careful checking and application of the documented procedure, which is tedious and error-prone. 

We should aim to automate this manual update step with a script that can be invoked when cutting an open-source release, to help achieve release automation. 

We should also evaluate to see if it makes sense to rotate some older release versions out from the set of Python compatibility tests when adding new versions in.