v4.0.0 ->strictAuthorization() by default

[janiscw]

Hi Dennis, hi team,

Thanks for the great work on Filament v4 — I noticed the new ->strictAuthorization() feature that is a very welcome addition.
I'd like to propose enabling strictAuthorization() by default for new Filament projects by adding it to the panel stub (or we introduce a global approach by adding it to the AdminPanelProvider).

A few reasons:

• No breaking change: This wouldn’t affect existing projects or upgrades, so it's safe as a default.
• Closed by default: Defaulting to a closed state aligns with the principle of least privilege. Explicit permission declarations help avoid surprises.
• Laravel’s policy generation is incomplete: For example, deleteAny isn’t generated by default:
  Github: Laravel Policy stub

Without strictAuthorization, this could lead to unintended access to bulk actions.

Curious to hear your thoughts.
Best,
Janis