feat: ability to reference version dependencies in CEL filtering

[adityachoudhari26]

[wandbjake]

We're writing dependencies for frontend like

{
  "dependencies": {
    "gorilla-guid": {
        "versionSelector": "version.metadata["api/gorilla-graphql-schema-sha256"] == "asd1234"
      }
  }
}

And there's two ways it could work

1. Minecart-side knowledge. I would have to read the deployed version of the gorilla deployment here and translate that into a filter on the dependent service. This is annoying though because now I have to parse the requirement back out of the CEL. That would look like
   version.metadata["api/gorilla-graphql-schema-sha256"] == "def5674" on the frontend filter CEL (based on looking at the metadata of gorilla and substituting the hash in). It's simple now but that's not guaranteed. For example if I wanted to add a date filter or any other things I have to know how to reverse them. The complexity just grows...

2. Passing in the target somehow to the version list endpoint (either a query param or a path param on a new endpoint). Versions would be evaluated in the same context they get evaluated for candidate releases and the CEL dependencies treated as opaque by minecart. I would need ways of getting filtered and unfiltered results here so I can show users that versions are being filtered by deployment dependencies but I can do two calls that's fine.

Strong preference for 2.