Drop legacy server-side search

[jdavcs]

We don't use this. Checked this before upgrading for SA2.0.

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[dannon]

Technically we should probably do a deprecation cycle this since it's a part of the API? (do you want to quickly add that to the 23.1 release notes?)

[mvdbeek]

It's probably a good idea to drop this, but this needs a deprecation announcement. That we don't use this in the client doesn't necessarily mean no-one uses.

[jmchilton]

I'm fine removing it... I'm not aware of any users. For some perspective this was added by Kyle Ellrott in the first couple years I was working for the project. He was working on a project to ship whole workflows to other Galaxy for execution. Still a noble goal and would solve all sorts of issues around temporary data retention, data locality, etc.. But I think the approach would not be based on search and GQL... I think we would want to ship the whole workflow request and refine the workflow invocation export for trusted internal import - the way we do for jobs internally.