IBX-10494: Refactored location filtering logic

[mikadamczyk]

🎫 Issue	IBX-10494

Description:

• Sorting uses the main location when needed and reuses an existing location join if it is already there. This keeps ordering stable even when the content has extra locations.
• Sort builders now order by the same aliases they select (content id/published/name, section identifiers/names, location_* aliases), cutting ambiguity.
• The filtering gateway runs the query directly with limit/offset; the old wrapper subquery was dropped as redundant.
• Location criteria skip extra joins when location is already in the query, and section/content sort builders add clear aliases.
• Tests now check location sorting with main vs. secondary locations and use getContentInfo()->getMainLocationId() everywhere.

For QA:

Documentation:

[konradoboza]

Code looks good but please evaluate @alongosz remark. I guess we don't have other way to distinguish queries apart from location alias? The current one looks a bit hacky but can go as-is I guess.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mikadamczyk]

Merged in #655