fix: keep view:cache working without the panel builder

[nessimabadi]

Fixes #204

Problem

php artisan view:cache (and php artisan optimize) fails in apps that use Flowforge without filament/filament:

InvalidArgumentException: Unable to locate a class or view for component [filament-panels::page].

view:cache compiles every view in every registered namespace. flowforge::filament.pages.board-page renders <x-filament-panels::page>, which only exists when the Panel Builder is installed. Since #86 the Panel Builder is only a suggested dependency.

Fix

• Move board-page.blade.php from resources/views to resources/panel-views, keeping the same relative path.
• In FlowforgeServiceProvider::packageBooted(), add resources/panel-views to the flowforge view namespace and to the flowforge-views publish tag only when Filament\Panel exists, the same check filament/support uses to detect the Panel Builder.

The view name stays flowforge::filament.pages.board-page, so BoardPage, BoardResourcePage and BaseBoard need no changes. Published overrides in resources/views/vendor/flowforge still take precedence.

Tests

• New test in ServiceProviderTest: no view under resources/views may reference filament-panels:: components. It fails on 4.x and passes with this change.
• The existing test that flowforge::filament.pages.board-page still resolves when Panels is installed passes.
• Full suite: 191 passed.
• Checked by hand in a real app with filament/forms and filament/tables but no filament/filament: view:cache fails on v4.1.4 and succeeds with this change.

composer analyse reports 7 errors on 4.x, all in files this PR doesn't touch.

🤖 Generated with Claude Code