When ConfigResolver is used either via dynamic settings or via direct getParameter call before SiteAccess context is resolved, it results in a warning, usually produced when trying to build dependency injection container.

This Epic groups discovered issues.