fix(ci): libclang dependency issues

[tabVersion]

…rfile

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

merging into #24004 if can help with zstd compile issue

--- stderr
--
 
thread 'main' (10738) panicked at /risingwave/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/bindgen-0.72.1/lib.rs:616:27:
Unable to find libclang: "couldn't find any valid shared libraries matching: ['libclang.so', 'libclang-*.so', 'libclang.so.*', 'libclang-*.so.*'], set the `LIBCLANG_PATH` environment variable to a path where one of these files can be found (invalid: [])"
stack backtrace:
0: __rustc::rust_begin_unwind
at /rustc/b925a865e2c9a0aefe5a2877863cb4df796f2eaf/library/std/src/panicking.rs:698:5
1: core::panicking::panic_fmt
at /rustc/b925a865e2c9a0aefe5a2877863cb4df796f2eaf/library/core/src/panicking.rs:80:14
2: core::result::unwrap_failed
at /rustc/b925a865e2c9a0aefe5a2877863cb4df796f2eaf/library/core/src/result.rs:1855:5
3: core::result::Result<T,E>::expect
4: bindgen::ensure_libclang_is_loaded::{{closure}}
5: std::sync::once_lock::OnceLock<T>::get_or_init::{{closure}}
6: std::sync::once_lock::OnceLock<T>::initialize::{{closure}}
7: std::sync::poison::once::Once::call_once_force::{{closure}}
8: std::sys::sync::once::futex::Once::call
at /rustc/b925a865e2c9a0aefe5a2877863cb4df796f2eaf/library/std/src/sys/sync/once/futex.rs:178:21
9: std::sync::poison::once::Once::call_once_force
10: std::sync::once_lock::OnceLock<T>::initialize
11: std::sync::once_lock::OnceLock<T>::get_or_try_init
12: std::sync::once_lock::OnceLock<T>::get_or_init
13: bindgen::ensure_libclang_is_loaded
14: bindgen::Bindings::generate
15: bindgen::Builder::generate
16: build_script_build::generate_bindings
17: build_script_build::main
18: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

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.
• I have added fuzzing tests or opened an issue to track them.
• My PR contains breaking changes.
• My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
• I have checked the Release Timeline and Currently Supported Versions to determine which release branches I need to cherry-pick this PR into.

Documentation

• My PR needs documentation updates.

Release note