Modify findNotes() to use V16 searchNotes() function

[viciousAegis]

Modify SearchNotes to be able to use both legacy and V16 functions

Pull Request template

Purpose / Description

Add support for using new backend method searchNotes()

Approach

By checking the schema version, the newer function is used on using V16. The newer searchNotes() function includes a parameter for sorting, which is not supported in legacy.

findNotes() function is modified in Collection so that V16 can be used when enabled

How Has This Been Tested?

On my phone by enabling V16 backend in settings.

Checklist

Please, go through these checks before submitting the PR.

• You have not changed whitespace unnecessarily (it makes diffs hard to read)
• You have a descriptive commit message with a short title (first line, max 50 chars).
• Your code follows the style of the project (e.g. never omit braces in if statements)
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the Google Accessibility Scanner

[Arthur-Milchior]

As a side note, I'd appreciate if you could remove part of the template that you don't fill, just so that I know what not to read and what information is relevant. Or ideally, fill it, e.g. to note that you can't test it in practice due to use of V16

[mikehardy]

Looks good to me, I'd like a look from @dae now
Also, not sure if this idea excites you or not @viciousAegis but I'd love for the V16 developer setting to be turned in to a toggle + preference for persistence as a separate thing. I believe we are at the point where easier testing would be a good idea, then hopefully near future we can move it from developer area to advanced

[mikehardy]

Verified both of dae's comments are addressed, thanks all for the review and @viciousAegis for the work - 🚀

[github-actions]

Hi there @viciousAegis! This is the OpenCollective Notice for PRs merged from 2022-08-01 through 2022-08-31

If you are interested in compensation for this work, the process with details is here:

https://github.com/ankidroid/Anki-Android/wiki/OpenCollective-Payment-Process#how-to-get-paid

We only post one comment per person per month to avoid spamming you, regardless of the number of PRs merged, but this note applies to all PRs merged for this month

Please note that GSoC contributions are okay for this process. Our philosophy is that our users have donated to AnkiDroid for all contributions. The only PRs that will not go through the OpenCollective process are ones directly related to am accepted GSoC project from a selected participant, since those receive a stipend from GSoC itself.

Please understand that our monthly budget is never guaranteed to cover all claims - the cap on payments-per-person may be lower, but we try to make our process as fair and transparent as possible, we just need your understanding.

Thanks!