build: address util.log.logcrash package rename

[rail]

After util.log was renamed to util.log.logcrash, the build system
stopped updating the Sentry environment variable properly. Instead of
setting it to the release version, it was falling back to the default
"development" value. As a result, all Sentry reports went to the
development environment bucket.

This patch addresses the name change.

Release note: None

[cockroach-teamcity]

This change is 

[knz]

oh WOW
very nice find and ... 🤦 on my side 😭

we'll want to backport this all the way to the earliest stable release that has the package rename (that would be v21.1)

[rail]

blathers backport 21.1 21.2

[blathers-crl]

Encountered an error creating backports. Some common things that can go wrong:

1. The backport branch might have already existed.
2. There was a merge conflict.
3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.

---

error creating merge commit from 235f9d0 to blathers/backport-release-21.1-75865: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 21.1 failed. See errors above.

---

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.}

[rafiss]

This is great! Does it also help explain why the Sentry->Github issue filer (on zapier) doesn't work since 21.1?

[knz]

Does it also help explain why the Sentry->Github issue filer (on zapier) doesn't work since 21.1?

I think that's why rail investigated this :)

[knz]

you'll need to do the backport manually for 21.1.

[rail]

Does it also help explain why the Sentry->Github issue filer (on zapier) doesn't work since 21.1?

Yes. I see in Sentry we trigger the Zapier webhook only when "environment starts with v".

[rail]

bors r=knz

[craig]

Build succeeded:

• GitHub CI (Cockroach)