Lockup prevent health check from Rails::HealthController

[oz-tal]

Deployments depending on a 200 response from Rails::HealthController to complete fail since a 302 is returned instead.

This internal controller was introduced in rails 7.1, and is currently part of the default setup of a new Rails app. It's notable to mention the out-of-the-box solution for deployment on a Rails 8 application is to use Kamal, where the application is bundled in a Docker image, and an healthy response from the controller is critical to complete the deployment process.

currently a workaround is possible by creating a custom health check controller where the lockup check is skipped.

I'm aware the project aim to keep compatibility toward older versions of Rails, and I'm looking into a fix that won't break anything. In the meantime, this bug should be documented.