chore(release): Boolean variables are passed as strings by Github Actions

[tyler-ball]

Summary

Performing this comparison actually turns a "true" string into a false. We already check for a string when consuming this environment variable so there is no need to perform it here.

Without this change, releasing packages causes them to only end up in the internal channels.

[curiositycasualty]

Removed labels for branches where release.yml doesn't exist.

[mashapedeployment]

The backport to release/3.2.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release/3.2.x release/3.2.x
# Navigate to the new working tree
cd .worktrees/backport-release/3.2.x
# Create a new branch
git switch --create backport-10343-to-release/3.2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 999f5bea44aa3092b61541a40adf1be81c6490b9
# Push it to GitHub
git push --set-upstream origin backport-10343-to-release/3.2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release/3.2.x

Then, create a pull request where the base branch is release/3.2.x and the compare/head branch is backport-10343-to-release/3.2.x.