Rework to split amp-manager from ION containers

[BrianSipos]

Closes #167

[DavidEdell]

Is the intention that ion-manager is now optional in favor of amp-manager? Or is it now required for most deployments to start the agent-compose.yml file alongside it?

As it stands now, I believe nginx (I'm working on removing this dependency) will fail if only docker-compose.yml is started with this changeset since ion-manager would be unavailable.

1. For the services status page (system_status.py), should amp-manager replace ion-manager, or be added in addition to it?
2. Same question for proxy settings in nginx (or it's replacement).

[BrianSipos]

Is the intention that ion-manager is now optional in favor of amp-manager? Or is it now required for most deployments to start the agent-compose.yml file alongside it?

As it stands now, I believe nginx (I'm working on removing this dependency) will fail if only docker-compose.yml is started with this changeset since ion-manager would be unavailable.

1. For the services status page (system_status.py), should amp-manager replace ion-manager, or be added in addition to it?
2. Same question for proxy settings in nginx (or it's replacement).

The actual AMP manager is now running under hostname amp-manager so anything that before addressed it via ion-manager needs to use the DNS name amp-manager instead. The manager configuration purpose, etc. has not changed though so should be usable in the same way just via different hostname.

[BrianSipos]

This PR should also separate the "anms" operational network from a "testenv" network between ION nodes (using static addressing) to make it fully clear that they are independent from each other.

[sonarqubecloud]

Quality Gate failed

Failed conditions
9 Security Hotspots

See analysis details on SonarQube Cloud