Only show compatible library versions when adding libraries through Fabric Environment in Workspaces

Customer wants to install several additional Python libraries, while the Microsoft Fabric Environment already includes pre-installed libraries.
The latest versions suggested by the environment UI are not compatible with the pre-installed libraries.
Since the UI requires users to manually select library versions (defaulting to the latest version), the customer must perform manual compatibility checks outside to determine which versions will work in the environment (with other pre-installed library versions).
Although the environment publishes successfully after installing the selected libraries, the notebook fails at runtime with the published environment due to incompatible library versions.
The customer expects behaviour similar to pip install, where dependencies are automatically resolved (ideal) or a warning/error is raised if incompatible versions are selected, rather than allowing the environment to publish successfully with conflicting dependencies.