Package-level loogging breaks custom logging configuration

objects.rateLimitedLog is initialized during package initialization phase, triggering log.once before log.InitializeLogger() has a chance to apply custom logging configuration. As result, the logging system does not accept custom configuration anymore.

entrypoint.TestCustomLoggingConfiguration() demonstrates the problem.

There are several ways to address the problem:

1. Lazy initialize the package-level logging variable objects.rateLimitedLog.

2. (preferred) Remove the package-level variable and replace it with an Application instance-level variable, which is also lazily initialized.

More details available here: https://yunikornworkspace.slack.com/archives/CLNUW68MU/p1704322291697499

Call stack that demonstrates the problem attached.