Filters for releases don't work as expected

### Environment SaaS (https://sentry.io/) ### Steps to Reproduce (I marked this as `Issues` since that's where the filtering is being done, but feel free to relabel if it fits better somewhere else) Opening on behalf of a customer (quotes are the customer's) > In our configuration, only debug builds may have a version that ends with d, so there will be debug with a version of 6.1.0d, for example, and a release with version 6.1.0, but never a mix of the two (i.e. can’t have a release version with a version that ends in d and vice-versa for debug and no d) >  > So as a possible UI fix, one way about this would be to allow the environment dropdown to automatically filter out un-selectable versions. For example, with the above, having the environment set to `debug` should only show 6.1.0d and 6.0.0d in the list of possible versions. (currently this is not the case -- setting the `environment` doesn't seem to result in further narrowing down the filters of which releases show. Instead, ALL releases show, even if those releases don't have any issues for a given environment. ### Expected Result > My expectation is that the items in the left box (project, environment, time range) are top-level filters that rule out things the custom-search can see <img width="1153" height="59" alt="Image" src="https://github.com/user-attachments/assets/71a378b4-172d-44b6-bae9-d88dd01a60d4" /> > To put this another way: It isn’t the case that you’re showing versions from across all projects in the custom search, so why aren’t environments and time ranges working in the same way to filter stuff out? (Not sure if there is a product reason for not doing this, but wanted to surface it to see it's an opportunity to reduce UI noise) ### Actual Result [see steps to repro above] ### Product Area Issues ### Link _No response_ ### DSN _No response_ ### Version _No response_