Combines legacy qv-pattern and advanced filter pattern in history index endpoint

[guerler]

Requires #17282. This PR combines the legacy q/qv and the advanced filter history index endpoints as discussed in the backend group meeting. In a follow-up the q/qv endpoint parameters will be deprecated.

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.

[davelopez]

I don't love this, I would have preferred an "adapter" step to try to convert those new query parameters to fit in the filter_query_params instead of the complete branching. Although I haven't checked if there is any limitation on this.
Anyway, I guess is better than having the extra route for now.

[guerler]

I agree with you, this is not very pretty. I think we have to decide wether to combine the two code paths or deprecate the legacy path moving forward. I would favor the latter, since this would also streamline the client request, which in the history panel, converts the modern search string to q/qv values as of right now.

[nsoranzo]

If we go ahead with deprecating q/qv, it would be nice if the new syntax still supported queries that we currently expose in BioBlend, e.g.:

https://github.com/galaxyproject/bioblend/blob/main/bioblend/galaxy/histories/__init__.py#L135

Not saying that it doesn't, I just wanted to flag it.
Then BioBlend can transparently use one syntax or the other, depending on the Galaxy version.