Package installation issues with pip in clean Docker environment

I am encountering unexpected behavior when trying to install the `ConfigSpace` library using `pip` in a clean Docker environment with Ubuntu 22.04 and ROS 2 (Humble) installed. The installation fails after displaying warnings about mismatched package/root metadata filenames.

The installer appears to discard recent versions and continues to backtrack to older versions, eventually stopping at version 0.6.1, which then fails to install.

I followed suggestions like [this Stack Overflow post](https://stackoverflow.com/questions/67074684/pip-has-problems-with-metadata), but the issue persists—no version of `ConfigSpace` is successfully installed.
Is there any way to avoid having to install the package inside a virtual environment (venv)?

**Steps to Reproduce:**
```
docker run -it osrf/ros:humble-desktop
sudo apt update
sudo apt install python3-pip
pip install ConfigSpace
```

**Logs:**
Below is the full log output when attempting to install ConfigSpace:
```
Collecting configSpace
Downloading configspace-1.2.1.tar.gz (130 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 131.0/131.0 KB 7.8 MB/s eta 0:00:00
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
WARNING: Generating metadata for package configSpace produced metadata for project name unknown. Fix your #egg=configSpace fragments.
Discarding https://files.pythonhosted.org/packages/0e/bc/2a53b259ec14101a42690992ea8fc2456edcacc73ede62f803dd3c4b0bdc/configspace-1.2.1.tar.gz#sha256=2fc1c4477f7839d38b53d8813c2581967df57ccd7d8b4b506e879a8835cb964c (from https://pypi.org/simple/configspace/) (requires-python:>=3.8): Requested unknown from https://files.pythonhosted.org/packages/0e/bc/2a53b259ec14101a42690992ea8fc2456edcacc73ede62f803dd3c4b0bdc/configspace-1.2.1.tar.gz#sha256=2fc1c4477f7839d38b53d8813c2581967df57ccd7d8b4b506e879a8835cb964c has inconsistent name: filename has 'configspace', but metadata has 'unknown'

```

No source files or tests are named. Start by reproducing the osrf/ros:humble-desktop Docker commands and the pip install ConfigSpace failure, then inspect the generated package metadata and build output; done means ConfigSpace installs successfully in that clean environment without a virtual environment.

Written by the indexing model from the issue text.