Move fixing oldest reqs to avoid merge conflicts. (#6921)
Move fixing oldest reqs to avoid merge conflicts. (#6921)

When releasing 0.33.1 and resolving merge conflicts between the candidate-0.33.1 branch and master, I had merge conflicts in the local-oldest-requirements.txt files. This is because the point release branch does not contain modifications to these files that landed in master because it happens later in the release script in the commit bumping version numbers which is not included in the point release branch.

I think having to resolve these merge conflicts is unnecessary and even a slight problem because it means that the "oldest" tests on the point release branch may still be using the latest version of certain components when they actually should be using an older version.

I fixed this by moving this code earlier in the script so the local-oldest-requirements.txt files are updated at the same time as the setup.py files.
letsencrypt/letsencrypt,stweil/letsencrypt,lmcro/letsencrypt,lmcro/letsencrypt,stweil/letsencrypt,letsencrypt/letsencrypt