fix(filter)!: resolve query names in the grammar again

[pdevito3]

Summary

• ParseFilter no longer rewrites query names in the filter text before the parse. The operator and logical alias passes stay.
• PropertyPathParser(config) reads a configured query name first (longest first), then a normal identifier path. The left side of a comparison and a property list use this parser.
• PropertyResolver.Resolve maps a query name to the property path of its mapping before the depth check and the member lookup. Arithmetic and property lists use Resolve, so a query name works there too.
• Each name maps one time. SortParser passes the raw sort name to Resolve. The right side of a comparison uses ResolveWithoutQueryName, because a query name on the right side is a value. The HasConversion check uses the resolved mapping.
• Every query name ignores case with the rules of the invariant culture. The current-culture lookup (GetPropertyInfoByQueryNameInCurrentCulture) is deleted.
• The regex check EnsureNoQueryNameOfAPropertyPreventedForFilterAndSort is deleted. A property with PreventFilter() and PreventSort() is now removed by its query name like any prevented property. It does not throw InvalidOperationException.

v1.14.2 behavior

QueryKit replaced each query name in front of an operator with its property path, on the raw text, before the parse. As a result:

• A query name inside a quoted value changed. Title == "first == x" compared Title with FirstName == x.
• A query name in a property list threw UnknownFilterPropertyException.
• A query name in arithmetic threw ArgumentException.
• A query name after a dot changed too. Author.name == "Lee" became Author.Title.
• A query name matched with the case rules of the current culture. In tr-TR, TIPALPHA did not match the query name tipalpha.

New behavior

HasQueryName("first") on FirstName, and HasQueryName("stars") on Rating:

Input	v1.14.2	This PR
Title == "first == x"	x => (x.Title == "FirstName == x")	x => (x.Title == "first == x")
(first, LastName) == "Paul"	UnknownFilterPropertyException: 'first'	x => ((x.FirstName == "Paul") OrElse (x.LastName == "Paul"))
(stars + 0) > 3	ArgumentException	filters by Rating
STARS > 3 in tr-TR	UnknownFilterPropertyException	filters by Rating

#132 bypass with #136

With #136 and the first commit of this PR together, a name could map two times. One time came from the query name, and one time came from Resolve:

Input	Configuration	Before the fix	This PR
Directions == Title	Directions query name title, Title PreventFilter	x.Directions == x.Directions	clause ignored
Directions _= Title	same	x.Directions.StartsWith(x.Directions)	clause ignored
sort title asc	Rating query name directions, Directions query name title with PreventSort	sorted by Rating	sort skipped

Migration

• If a client sent a query name in another letter case and relied on the current culture (for example tr-TR), the name now matches with the invariant rules.
• If a client caught InvalidOperationException for a query name of a property with PreventFilter() and PreventSort(), the clause is now removed (or true == true with IgnoredClauseBehavior.ReplaceWithTrue).

Tests

• Unit PropertyResolverTests: prevented_property_on_the_right_side_is_not_compared_when_another_query_name_matches_its_name (== and _=), prevented_sort_property_is_skipped_when_its_property_path_is_another_query_name, and the two property_prevented_for_filter_and_sort_is_removed_by_its_query_name* tests (they expected a throw before).
• Unit AliasCultureTests: I/i matches in tr-TR and en-US in a comparison, a property list, and a sort. ı and İ do not match I and i.
• Integration (Postgres): prevented_property_on_the_right_side_is_not_compared_when_another_query_name_matches_its_name, query_name_in_a_property_list_is_filtered, query_name_in_arithmetic_is_filtered, and query_name_with_i_matches_its_upper_case_in_tr_tr.
• dotnet test: 527 unit tests and 324 Postgres integration tests pass.