[GLUTEN-13329][VL] Match the TencentOS Server os-release name in the shared library loaders

[LuciferYang]

What changes are proposed in this pull request?

Since #10774, the CentOS shared library loaders match TencentOS with osName.contains("tencentos"), where osName is the NAME field of /etc/os-release. TencentOS Server reports NAME="TencentOS Server", so the check never matches, and with spark.gluten.loadLibFromJar=true loading fails with "Cannot find SharedLibraryLoader". Before #10774 the check ran on the whole os-release text and matched ID="tencentos".

This lowercases the name with Locale.ROOT before the check, in Velox's SharedLibraryLoaderCentos8 and in Bolt's SharedLibraryLoaderCentos7 and SharedLibraryLoaderCentos8. Velox has had no CentOS 7 loader since #13336. The version checks are unchanged: TencentOS 3.2 goes to the centos8 loader, 2.4 goes to Bolt's centos7 loader, and no other registered loader accepts the TencentOS name.

How was this patch tested?

Added SharedLibraryLoaderCentosSuite, which checks Velox's centos8 loader against the NAME and VERSION values TencentOS Server 3.2 reports, and that 2.4, 3.1 and 4.2 are rejected. The first case fails without this change. The Bolt copies get the same one-line change and compile, but no test or CI job covers backends-bolt.

Was this patch authored or co-authored using generative AI tooling?

Yes. Generated-by: Claude Opus.

Related issue: #13329.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[philo-he]

LGTM. Please rebase and resolve code conflicts. Thanks.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[LuciferYang]

Thanks @philo-he. Merged main in to resolve the conflict. #13336 removed the Velox CentOS 7 loader, so on the Velox side the fix and the test now only cover the centos8 loader (TencentOS 3.2). The Bolt copies of both loaders keep the change.