Description of problem:

How reproducible:

Always

Is this issue a regression from an earlier version:

Yes

Steps to Reproduce:

1. Setup and configure Satellite for IoP Advisor and Vulnerability service

2. # hammer ping

Actual behavior:
hammer ping doesn't display insights services for advisor and vulnerability services for IoP enabled Satellite.

Expected behavior:
hammer ping displays insights services for advisor and vulnerability services for IoP enabled Satellite.

Business Impact / Additional info:

Workaround: foreman-maintain service restart, and then check hammer ping

Acceptance Criteria

1. The Smart Proxy paradigm should be respected. The way for a system to determine if a certain function is available, such as IoP, should be through querying the availability of smart proxy features, NOT through installer configuration or settings.
2. When smart proxy feature detection is unreliable, such as during app initialization or plugin initialization (engine.rb / plugin.rb), it needs to be worked around.
   1. Assembling the main nav - This already takes a lambda, so this one is taken care of.
   2. Registering the Ping extension - The Ping extension should be registered regardless of IoP, and should be modified to return an empty Hash ({}) in non-IoP cases.
   3. Registering app metadata for population of ForemanContext - Foreman should be altered to query the app metadata via lambda, rather than only the initial rendering of the react component.
3. Switching between IoP and non-IoP should not require a service restart. Everything should work. Ideally, not even a browser page reload should be needed, but that is acceptable if we can't avoid it.