feat: migrate to f4

[KilianTrunk]

No description provided.

[SlimDeluxe]

Just curious, most of the files changed are simply using imports instead of FQCN names for classes in the code. How was this triggered? By the upgrade tool, your editor... ?

[SlimDeluxe]

Same here, please update the tests workflow.

[KilianTrunk]

@SlimDeluxe correct, these changes are from the upgrade tool from filament. it sucks it didn’t really fix much stuff (had to do it manually), only changed these imports and told me what to upgrade in the composer

[SlimDeluxe]

• There's an error on the users page (wrong class import)
• getPermissionPrefixes() do not seem to be respected anymore, all permission groups now include all permissions for a resource
• "My settings" page is now half the width
• There's an error on the profile page

[SlimDeluxe]

I see the test failing since it's pulling the common package from the main branch on upstream.
We have 2 options:

1. Set the repo and branch to your own (in composer.json)
2. Make sure UI has no problems, CLI tests work locally and then just wait for f4 branch to be merged in common