Update release.yml to manually run tag-release.yml

[rekhoff]

This PR addresses #5632 which calls out the issue that apparently it is expected behavior that, even though the tag-release.yml workflow is supposed to run on release publish, this will not happen if the release was published by a workflow action.

Description of Changes

Adds a step to release.yml that manually runs tag-release.yml, and then adds additional logic to tag-release.yml that can take input coming from the release.yml workflow.

This change also attempts to preserve the existing DryRun path so the messages will not be sent on a dry run.

API and ABI breaking changes

No changes.

Expected complexity level and risk

Low. Only two GitHub Actions workflow files are modified. The dispatch uses gh workflow run --json, and the publish-github-release job already has the required actions: write and contents: write permissions.

Testing

• Other than reviewing the workflow, no real testing has been performed with these workflow changes.

• If desired by reviewer, we could change the WebHook back to the internal, so we can validate the behavior during the next release without fear of causing a noise to the public Discord.