Feat / Implement User Access Control

[thapacodes4u]

Related Ticket FR-9
Related Ticket FR-10 "I think what we are trying to achieve in that ticket is solved by this as well just the approach is different. So you can treat this PR handling both of those ticket"

[codecov-commenter]

Codecov Report

❌ Patch coverage is 70.42254% with 21 lines in your changes missing coverage. Please review.
✅ Project coverage is 66.03%. Comparing base (6999906) to head (7f4e29c).

Files with missing lines	Patch %	Lines
src/Pages/Auth/Login.php	0.00%	16 Missing ⚠️
src/Http/Middleware/CheckFrontendFeatures.php	84.84%	5 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main       #6      +/-   ##
============================================
+ Coverage     62.90%   66.03%   +3.13%     
- Complexity       23       44      +21     
============================================
  Files             5        7       +2     
  Lines           124      159      +35     
============================================
+ Hits             78      105      +27     
- Misses           46       54       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[thapacodes4u]

@SlimDeluxe Filament's tenant system (->tenant() with ->tenantDomain()) was incompatible with guest access because it requires authenticated users to pass the canAccessTenant() check, which caused 404 errors for guests trying to access the root path.

To resolve this, I removed the Filament tenant configuration and implemented tenant awareness manually using the existing Registry pattern. The CheckFrontendFeatures middleware now uses Registry::getSite() to get the current site context, and all settings queries filter by site_id to maintain tenant isolation. This approach works for both authenticated and guest users while preserving full tenant-scoped access control.