fix: switch the filesystem disk to s3 when RustFS is wired

[geodro]

Picking RustFS for a Laravel site, from setup or from the suggested service card on the dashboard, wired the AWS keys into .env but left FILESYSTEM_DISK on local. The app kept writing to the local disk and the bucket lerd had just created stayed empty. The preset does carry FILESYSTEM_DISK=s3, but a framework that maps a service gets only its own vars, and Laravel's mapping never listed the disk.

Laravel's rustfs mapping now writes the disk key too. Laravel 9 and later read FILESYSTEM_DISK, 6 to 8 read FILESYSTEM_DRIVER, so each version gets the key it actually reads, and the detect rule on 6 to 8 now looks at that key as well.

Statamic, Winter and Lumen run on Laravel and read the same AWS keys, yet they had no rustfs mapping at all and only got the preset's keys through the fallback. They now map it the same way, with the disk key matched to the Laravel version underneath. Statamic 3 spans Laravel 6 to 10, so it writes both keys. Winter 1.1 hardcodes the local disk, so only 1.2 actually switches.

Symfony stays as it is. S3 there goes through a bundle whose env names the app chooses, so there is no standard key to map.