feat: S3 restore

[andrasbacsai]

Summary

Fixed the S3 restore button that was always disabled by implementing proper client-side reactivity using Alpine.js, and improved security by using the ownedByCurrentTeam() scope instead of manual team verification.

Changes

View File (resources/views/livewire/project/database/import.blade.php)

• Added Alpine.js entangle() bindings for s3StorageId and s3Path
• Changed button disabled binding from PHP :disabled to Alpine x-bind:disabled for reactive updates
• Kept inputs as deferred wire:model (no .live modifier) to avoid unnecessary server requests

Component (app/Livewire/Project/Database/Import.php)

• Updated checkS3File() method: Use S3Storage::ownedByCurrentTeam()->findOrFail() instead of ::findOrFail()
• Updated downloadFromS3() method: Use S3Storage::ownedByCurrentTeam()->findOrFail() instead of ::findOrFail()
• Removed redundant manual team verification since the scope handles it automatically

Why This Works

The button now uses Alpine.js reactivity via `$wire.entangle()` bindings, which:

• Syncs Livewire properties to Alpine state without hitting the server
• Allows `x-bind:disabled` to reactively update based on user input
• Avoids the overhead of `.live` modifier which would trigger server requests on every keystroke

The security improvements use the existing `ownedByCurrentTeam()` scope which:

• Automatically filters S3 storages to only those belonging to the current team
• Eliminates redundant manual team ID verification code
• Follows the same pattern already used in `loadAvailableS3Storages()`

Testing

The button should now:

• Be disabled when the page loads (no storage selected, no path)
• Enable when both S3 Storage and S3 File Path are filled in
• Remain responsive as the user types/selects without server latency