Bug description

When using scoped disks/driver from a disk that has been defined in the tenancy.filesystem.disks config. The resolved instances of those disks are not forgotten when initializing or reverting the FilesystemTenantBootstrapper and therefore persisting the previous tenant path prefix withing the application lifecycle.

Steps to reproduce

1. Define a tenant disk in config/tenancy.php

return [
    // ...
    'filesystem' => [
        'disks' => ['local'],
    ],
    // ...
];

2. Define a scoped disk in config/filesystem.php

return [
    // ...
    'disks' => [
        'tenant-public' => [
            'driver' => 'scoped',
            'disk' => 'local',
            'prefix' => 'app/public',
            'visibility' => 'public',
        ],
    ],
    // ...
];

3. Create two tenants
4. Initialize one tenant and request the path using the Storage facade
5. Initialize the second tenant and request the path using the Storage facade

Expected behavior

Disks scoped to a tenant bootstrapped disk should also be forgotten on tenant initialization

Laravel version

11.46.0

stancl/tenancy version

3.9.1