Interactive workflow creates a commit that eventually fails the "is a release" check

When you create a release branch via `yarn create-release-branch -i`, the commit that it creates is called "Update Release X.Y.Z". If you then create a pull request and merge that pull request, it will _not_ result in initiating the release workflow, because "Update Release X.Y.Z" is not a valid title for a release. Many engineers have worked around this by retitling the PR upon creating it, but that is not ideal. The tool ought to name the commit "Release X.Y.Z" instead.

Start at the `yarn create-release-branch -i` command entry point and trace where the release-branch commit message is assembled. Update the generated title from `Update Release X.Y.Z` to `Release X.Y.Z`, then run the command's existing tests or a manual interactive workflow to verify the merged commit can initiate the release workflow.

Written by the indexing model from the issue text.