Filter upper-constraints content

As part of the deployment process, we store upper-constraints content on the repo server, while caching it locally on the deploy host.

With that, we maintain a global-requirements, which may be conflicting with upper-constraints at some points.

In order to avoid such conflicts, we can filter out our cached version of upper-constraints to not contain any records from the global-requirements, and allow global-requirements to be a source of truth.

This way we cal solve a numpy conflict for Ubuntu 26.04, as it has incompatible version pinned in u-c, but also puts us in control for any further usecases.