## Summary:

One part of our publish process we have not yet automated is setting the
`v0.xx-stable` and `next` tags when a new release is promoted or
demoted. Let's automate this by specifying additional tags in our CI
that should be set when we publish a release. Now, a new `latest` or
patch to `latest` will also always set is `0.xx-stable` tag.

Note: Previously, if `0.xx` was tagged as `latest`, we would not have
had a `v0.xx-stable` tag. Now we will always have both `latest` and the
`0.xx-stable` tag.

## Test Plan:

I duplicated this change to
#2800 and
#2801 . We can look
at the dry run output for both to make sure release is behaving as
expected.