Add multi-site support to filter options

[taylanunutmaz]

This pull request includes changes to ensure taxonomy queries are filtered by the current site in the HandleStatamicQueries and IsSortable traits. The most important changes include adding the Site facade and modifying methods to include the site filter in taxonomy queries.

[Biostate]

Your approach works but has some issues. Specifically, in a multi-site project, it uses the translatable slug of a taxonomy. However, my collection stores the taxonomy slug in the default locale.

Example

I have a Projects collection, and I’ve added a Country taxonomy to it. When I attach a country, the collection stores the default locale slug for that country.

USA Country

• English: slug → usa
• Turkish: slug → abd

A Project Entry

• English taxonomy slug: countries: usa
• Turkish taxonomy slug: countries: usa (Same as English)

Issue

When querying in the Turkish site using "abd", the results won't be found because the project is stored with countries: usa.

Solution

You need to modify the code to always retrieve the taxonomy slug from the default locale:

- $term->slug() => $term->title(),
+ $term->inDefaultLocale()->slug() => $term->title(),

This ensures that the taxonomy slug is consistently fetched from the default locale, preventing mismatches across different site languages.

[afonic]

Thank you for this. Will add some multisite tests in this PR and merge it in the next release.