Solver listing filters by key and version_display patterns

[pcrespov]

Follows up from #7678 (comment)

@mguidon quote

No sure what the status is regarding this ITISFoundation/private-issues#49

I need to be able to get a list of solver-key:solver-version by filtering on the display_version. For instance:

Ideally, I could ask for filter: { "key": "isolve*", "display-version": "9.0.0*"} and I get back all of these:

isolve-cpu:9.0.0
isolve-gpu:9.0.0-rc.2
isolve-mpi:9.0.0-rc.1
isolve-mpi:9.0.0-beta.2
isolve-cpu:9.0.0-beta
isolve-gpu:9.0.0-alpha

@pcrespov quote

1. ITISFoundation/private-issues#49 is completed but I only see that version_display was added to Program and > NOT to Solvers. I think there was a miscommunication here (we can fix that tomorrow though)
2. For starters you can inject these values as part of your custom metadata as you create the job and use the > filters in this PR to list them
   • 💡 we could automatically inject it upon creation as well
   • GET /solvers/-/releases/-/jobs?metadata.any=solver_name:isolve*9.0.0*
3. Tomorrow I can also start a new PR with dedicated filters and even provide the version display in the Solvers (in > case you need it!)
   • 💡 GET /solvers/-/releases/-/jobs?solver_name.any=isolve*&version_display.any=1.2*&version_display.any=2.*

---

• list solvers filter by solver_id value/wildcard and display-version value/wildcard
• FIX /solvers?solver_id="*isolve_mpi" should return ALL versions and not only latest!
  • Future should be GET /solvers/isolve-gpu:9.0.0-alpha including key&version as part of the solver_id isntead of GET solvers/{solver_id}/releases/{release_id}
• follow up to arrange RPC interface schemas for the catalog correctly