Develop new static service publishing strategy for deployments to UAT/Prod

[shawncrawley]

PR #894 was merged a few months back. A main goal of that work was to get rid of the part of our deployment workflow that would spin up the hv-vpp-*-viz-pipeline EC2 and kick off a script to publish all of the services prior to kicking off the pipelines. I just barely realized that if we retire that part of our workflow, we are going to have to come up with a new way to automate the publishing of our suite of static services on each deploy, since that original workflow took care of it.

Whether we keep that part of our workflow around just for the static services or come up with something new, the bottom line is that we have to solve this problem or else all static services will not get republished on deployments.

Note: We are including the new bridge_centroids system for the pending 2.1.8 so we will need at least a temp work around it to get it to TI, UAT, and Prod

[RobHanna-NOAA]

Won't we need this for TI as well? The ability to publish and test in TI?