[PIR Action] Improve observability for connect web panels

Currently, connected web panels are very fragile. `atl.general` and `atl.footer` web panels are rendered on different pages. It's not clear where and how these panels should be rendered.

Assuming that we have improved documentation for web panels, we should make sure that any newly introduced logic doesn't change the described behavior.

This can be done by covering all use cases with e2e tests, visual regression (VR) tests or by providing and monitoring metrics that can detect such changes.

As a result of this ticket, we should have clear vision on how we improve observability for connect web panels