Force resolvers cache invalidation to central context

[darkons]

Bug description

The tenancy cache is not invalidated when the tenant is updated from tenant context due to the CacheTenancyBootstrapper.

Maybe it would be a good idea to force the use of the central cache in the invalidateResolverCache method of the Tenancy class.

Steps to reproduce

Update the current Tenant model from some tenant context controller:

class SomeTenantContextController extends Controller
{
    public function update(Request $request): RedirectResponse
    {
        tenant()->update([
            'map_center_lat' => $request->map_center_lat,
            'map_center_lng' => $request->map_center_lng,
        ]);
    }
}

Of course, using the tenancy()->central() helper method works correctly because CacheTenancyBootstrapper is reverted.

Expected behavior

The Tenant cache should be invalidated.

Laravel version

12.0.3

stancl/tenancy version

4.x commit 8cd15db