Make queryUI on ViewV2 something you can write on its own, and query gets filled in for you

[samwho]

Description

This PR is on request of @aptkingston, it makes it such that the various view APIs allow the frontend to only work with queryUI and can ignore query.

Here's broadly what's happening:

• On view create/update, if you set queryUI it will generate query for you (regardless what you specify for query, it will get overwritten because queryUI is the source of truth).
• On view fetch (either directly or through the table), if there is a query but no queryUI, queryUI will get generated from query*.

*This only happens if query is of type LegacyFilter[], which is true of all ViewV2 in prod on Budicloud today (we checked). When we convert queryUI to query, we don't convert to a LegacyFilter[] but instead to a SearchFilters. There's currently no function to convert between SearchFilters and UISearchFilter (renamed from SearchFilterGroup) because it's technically lossy, and in theory we don't have to because from now on the frontend will always set queryUI.

I'm sorry for how confusing this all is. There's a lot of history around this part of the codebase and I'm doing the best I can to slot in new requirements to an already complex part of the code.

Feature branch env

Feature Branch Link

[qa-wolf]

QA Wolf here! As you write new code it's important that your test coverage is keeping up.
Click here to request test coverage for this PR!

[mike12345567]

LGTM - very nice work, great to get all the tests updated as well!