[Bug]: GLIBC Version Compatibility Issue: Avalanche CLI Fails to Run Due to Missing GLIBC_2.32, GLIBC_2.33, and GLIBC_2.34 on Linux

**Describe the bug**

The Avalanche CLI fails to run due to missing GLIBC versions. After installation, running any avalanche command returns an error indicating that required GLIBC versions (GLIBC_2.32, GLIBC_2.33, GLIBC_2.34) are not found on my system.

**To Reproduce**

Run the following command to install the Avalanche CLI:

curl -sSfL https://raw.githubusercontent.com/ava-labs/avalanche-cli/main/scripts/install.sh | sh -s

After installation, update the PATH variable:

export PATH=~/bin:$PATH
Run avalanche --help or avalanche --version to verify the installation.

**Expected behavior**
I expected the avalanche command to display the help or version information without errors, indicating a successful installation and working environment.

**Screenshots**

**Logs**
Below are the error logs displayed when running avalanche --help or avalanche --version:

avalanche: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by avalanche)
avalanche: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by avalanche)
avalanche: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by avalanche)

**Operating System**
OS: Linux (Ubuntu)
Device: HP 250 G8 Notebook PC

**Additional context**

It appears that the Avalanche CLI requires GLIBC versions that are not installed on my system, which could suggest a compatibility issue or the need for an alternative installation method. Possible workarounds like upgrading GLIBC directly could be risky for my system’s stability. I'd appreciate guidance on whether a Dockerized solution, static binary, or alternative approach might be available.

Reproduce the failure by following scripts/install.sh on an Ubuntu system with the reported GLIBC versions, then run avalanche --help and avalanche --version. Inspect the installer and distributed CLI artifact to identify the compatibility boundary; done means the supported Linux installation runs without missing-GLIBC errors or the supported alternative is documented.

Written by the indexing model from the issue text.