Add crate_universe into new_release about drake

[jwnimmer-tri]

Maybe to clarify... the existing upgrade.sh script in that same directory performs the upgrade, by editing the relevant files. It doesn't do anything in terms of adding to git, nor is able to check whether anything needs an upgrade.

I think the behavior we're looking for here is that as part of the monthly process we always run this upgrade.sh and (assuming something changed) we stage and commit that.

[jwnimmer-tri]

The real outcome we want is that we don't forget to keep running this.

Instead of changing new_release, maybe instead we should make an issue template for the monthly task, and the template can have a checkbox to remind us to run it. The template should prompt to encourage itemizing the PR numbers(s).

We seem to all like the idea of a template, so @mwoehlke-kitware will do that first.

[jwnimmer-tri]

Another idea: the issue template could remind us to check for a newer bazel version (or, we could have new_release automate that check).

[jwnimmer-tri]

Remaining work: make a nice issue template to simplify our lives. Checklists rule!