[Python APIView] Process for tooling update

[lmazuel]

Tooling update can create diff on the views in two ways:

• View "glitches" that didn't interfere with the API approval
• View major bug fixes, that now shows API that should have been reviewed but have been missed.

For those reasons, we believe we should have a process in place to tooling update:

• Tooling updates should trigger an email of diff update to review for architects, to confirm what the tolling discovered
• Tooling updates should not happen on code complete week for clarity
• Tooling updates should start by using new version of the tool on the same version of the code, to clarify if there is a diff induced by the tool itself, before using a new version of the code. Otherwise it is not clear where the diff is coming from (from new code or new toling or both)
• Tooling version should be pinnable as necessary for clarity

[praveenkuttappan]

APIView changes are not deployed to production in last week of release unless there is a critical issue that blocks release. We will ensure this is followed thoroughly.

Most of the time parser version is updated when a change is made in Python parser that makes a view change. APIView also has a mechanism to update existing reviews using this new parser so diff against a new revision is using same parser version. I have a found a gap in this process and updated the code to refresh all automatic and pull request revisions when a new parser version is available. We will keep an eye on this change if this is not enough. I have noticed that this fix has already auto updated python reviews to latest parser version today when a new change is made to 0.2.5.