fix: add clang for release script

[huangjw806]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[BugenZhao]

Have we tested it?

BTW, I'm curious why we use different scripts for building RisingWave for binary releases and Docker releases.

[huangjw806]

BTW, I'm curious why we use different scripts for building RisingWave for binary releases and Docker releases.

This is because compiling binary requires using a lower version of glibc, otherwise it will not run in different environments.

#4556

[huangjw806]

Have we tested it?

test pipeline: https://buildkite.com/risingwavelabs/docker/builds/15068

[huangjw806]

fixed by #14817

[BugenZhao]

This is because compiling binary requires using a lower version of glibc

Can the lower version of glibc be adopted for the docker image as well?