Where possible, allow "space-less" omr query entry

Currently, OMR search queries require spaces between terms (for example, a query for the relevant pitch sequence is "c d e" rather than "cde"). In most query types, there's no reason this needs to be the case as the division of the query string into relevant terms can be intuited.

Start by locating the OMR query-entry and parsing logic, then trace how space-separated terms such as "c d e" are divided. Compare that behavior with the equivalent "cde" input across query types and identify where term boundaries can be inferred. Done means supported query types accept the space-less form without changing query types that require explicit separation.

Written by the indexing model from the issue text.