fix(config)!: keep a query name in a nested path in alias replacement

[pdevito3]

For later consideration in a major version. Do not merge now. #122 restored the v1.14.2 match to keep v1.x non-breaking. This PR takes the fix back.

Summary

 QueryKitPropertyMappings.ReplaceAliasesWithPropertyPaths
-  regex: \b{QueryName}\b(?=\s*{op})
+  regex: (?<!\.)\b{QueryName}\b(?=\s*{op})

• v1.14.2: The public method QueryKitPropertyMappings.ReplaceAliasesWithPropertyPaths replaces a query name anywhere in front of an operator, also after a dot.
• New: A query name after a dot is a segment of a nested path. The method keeps it.
• Why: The segment after the dot belongs to another type. When name is the query name of a top-level property, the old match changes Author.Name to Author.Title, which is a wrong path.

Evidence

With config.Property<Recipe>(x => x.Title).HasQueryName("name") (the match ignores case):

ReplaceAliasesWithPropertyPaths("""Author.Name == "x" && name == "y" """)
  v1.14.2 and main: Author.Title == "x" && Title == "y"
  this PR:          Author.Name == "x" && Title == "y"

The restore test is renamed back to alias_replacement_does_not_replace_a_query_name_in_a_nested_path and expects the new result.

dotnet test on this branch: all unit and integration tests pass, 0 failures.

Merge Danger

Door: two-way

The change is one lookbehind in one regex.

Blast Radius: direct callers

The parser does not call this method, so filters do not change. Only consumer code that calls ReplaceAliasesWithPropertyPaths directly sees the new result.