Correct the liveness probe path

Since NEV-211, we've updated both the readiness and the liveness probe paths to /arendergwt/health/records which is a healthcheck that reflect the status of the entire stack.

This can cause trouble when a pod in the stack takes some time to restart for instance.

Maxime Veron advised us to use a static resource /arendergwt/gwt/standard/standard.css as a liveness probe path to mitigate the issues when the whole service is up and to keep the one we have currently for the readiness check.

This will allow detecting the previewer as ready when the whole stack is ready and to keep it up while the stack is running independently from the whole stack availability.