python - pr

[scbedd]

This PR is the actual implementation of a expanding/contracting public pull request build.

python - pr will replace all existing python - <service> - ci builds in public.

To manually run the the python - pr build instead of for a PR, one can manually queue it and set the service to the package that should be scanned.

TODO:

• Initial yml updates
• Verify pull request conditions vs "auto" service directory argument
  • Do we need to be worried about pull request logic showing up if we /azp run a job? Should I pull back to only honor the auto instead of Build.Reason?
  • No. @weshaggard would prefer that the same expandable logic (including beyond their package directory) is possible. This is now in place.
  • We also need to change this such that ServiceDirectory targeted also build dependent packages.
• Handle verify readme error
• Ensure that verify changelog static analysis actually runs (notice it's all skipped currently)
• Handle issues with detect api changes
• Test an internal core invocation from a package, ensure that the expansion still works
• Test a nightly livetest build to verify that nothing from previous methodology is broken -- check
• Test template release build -- check
• Test nightly scheduled build to verify package property updates

[weshaggard]

@scbedd when you think you are ready can you call a meeting with @benbp and I so we can do a live review of all the changes. I want to make sure we both fully understand these.

[scbedd]

Closing to prevent pounding on the agent pool while I clean up python - pr from the latest updates.