Drop Puppet class initializer on startup
On start up, the Puppet implementation updates all environments and retrieves the classes for each of them. This can be a fairly expensive operation. Warming up the caches is only relevant if caching on the Puppetserver is enabled (defaults to false) and if the environment doesn't change. For most deployments, this only adds overhead and doesn't actually improve performance.
Fixes #30856 - Drop Puppet class cache initializer
Retrieving all classes for all environments only makes sense if caching
is enabled on the Puppetserver. By default this is the case. Even if
this is not the case, it only works for environments that don't change.
It's sufficient to lazy load this.
This saves load on start up of services.