Is there some reason why `HoconApplicationConfig` ...

# ktor

[obobo]

Is there some reason why HoconApplicationConfig doesn't expose the underlying Config object? It's immutable, and the Hocon API is much richer than `ApplicationConfig`'s. In particular I needed access to the Config object to expose a Spring-like /env management endpoint, so I had to instance the Config manually then pass it into a HoconApplicationConfig, then pass the down to a module. Being able to access the Config directly, after a cast would make this much easier.