Develop an OpenStack-Helm endpoints catalog

[eak13]

Problem description
As an operator, I want the ability to specify OpenStack-Helm software/component endpoints in Airship 2 in a way that is consistent to how I manage OSH endpoints in Airship 1 today, so that I can maintain OSH endpoints in a manner that's consumable by OSH.

Proposed change
The OSH endpoint catalog should be formatted in a similar fashion to what's out there today with one major exception. While the format of the data: section needs to remain intact, the substitution section needs to change to leverage the kustomize/replacement transformer capabilities.

At a minimum, the endpoint list should also be updated to remove any Airship 1 components like armada, deckhand, etc.

The current AS1 endpoint catalog can be found here.
https://raw.githubusercontent.com/airshipit/treasuremap/master/site/seaworthy/software/config/endpoints.yaml

Per @mattmceuen suggestion, created https://storyboard.openstack.org/#!/story/2008493 in osh-deployments to create the endpoint catalog there. This issue will be used to track upstream.