run count and search concurrently, but don't wait for count to be done

[philvarner]

Related Issue(s):

• count and search operations can be done concurrently rather than sequentially #76

Description:

Previously, the count and search ES requests were run sequentially, so every search request was delayed for as long as it took to get the complete count of matches. This is an optional field in the Context Extension, and is generally not worth waiting on.

Now, the code creates tasks for both the count and search, and only awaits the search task. If the count task isn't completed by the time the search is finished and its results serialized to Items, the count is ignored and the items. are returned.

Also note that we do not cancel the count task, so that it will complete and the ES cache will be populated with the results for the next similar query.

PR Checklist:

• Code is formatted and linted (run pre-commit run --all-files)
• Tests pass (run make test)
• Documentation has been updated to reflect changes, if applicable, and docs build successfully (run make docs)
• Changes are added to the changelog

[philvarner]

actions aren't running, but this passed locally (though it also passed locally before I made the change). We'll see in main if there are any problems.