Update 0.9 branch release streategy

[seanpmorgan]

Combines changes from #1760 and #1762

• Use Github token for Bazel API requests
• Pin pip to 19.0 during release
• Test against 2.2.0 stable (still build against 2.1.0 though)

Unblocks #1810

[bhack]

Ok I think that we need to remove or modify this to support a list tools/update_release_version.sh

[gabrieldemarmiesse]

Thanks @seanpmorgan !

[gabrieldemarmiesse]

I think we broke the CI of the 0.9 branch with this pull request. I think it must have been a problem with indentation in the yaml. The tests are not running in the different OSs. I'm just noticing now.

I have the official title of worst reviewer ever.

@seanpmorgan do we forget about the 0.9.2 release? Let's push then for a release of the 0.10 as soon as possible, I don't think there is anything blocking it. It doesn't really matter if #1807 is not merged yet.

[seanpmorgan]

I think we broke the CI of the 0.9 branch with this pull request. I think it must have been a problem with indentation in the yaml. The tests are not running in the different OSs. I'm just noticing now.

I have the official title of worst reviewer ever.

@seanpmorgan do we forget about the 0.9.2 release? Let's push then for a release of the 0.10 as soon as possible, I don't think there is anything blocking it. It doesn't really matter if #1807 is not merged yet.

Yeah I think that's the best course of action. Sorry I missed the CI getting skipped as well. In either case the deprecation warning for custom activations landing on 0.10 is fine since that still gives 2 releases