Alias health in lieu of a separate binding

[mabdullahsari]

Hey 👋

This PR addresses an issue that arises when using Laravel's Container Events.

Given the following excerpt from an actual ServiceProvider:

public function register(): void
{
    $this->app->afterResolving(Health::class, $this->registerChecks(...));
}

private function registerChecks(Health $health)
{
    $health->checks([
        CacheCheck::new(),
        // ommitted for brevity...
    ]);
}

Triggering the health:schedule-check-heartbeat command makes the application crash with the following exception:

Spatie\Health\Exceptions\DuplicateCheckNamesFound

Digging a bit deeper reveals that the command eventually makes use of the Health Facade on L17.

The problem with this, is that the Facade makes use of the health binding instead of the singleton Health::class binding. A kinda hidden and notorious behaviour of the Facade class is that it creates a completely separate service context, ie. non-singleton bindings will be treated as singletons when making use of a Facade.

---

TL;DR By aliasing health to Health, we can ensure the same instance is used across all possible use cases.

(I have also removed the Closure defined on L39 because the IoC container will be able to auto-wire that without any problems.)

Thanks!

[freekmurze]

Thank you!