Support spaces and negation in match-near search operator

The 'match near' search operator currently does not accept spaces within its search string, which prevents customers from constructing multi-term proximity queries such as combining a keyword phrase with parameters like span and order settings. Additionally, there is no 'does not match near' operator available for excluding results based on proximity criteria. This enhancement proposes updating the 'match near' operator to support spaces within its query syntax and introducing a complementary 'does not match near' operator for negated proximity searches. Customers building Dynamic Search criteria or Dynamic Device Group membership rules would gain more flexible and precise control over proximity-based searches, reducing the need for workarounds when defining complex search or exclusion logic.