Deprecate and replace the pod-configs repo

Change the way Jenkins jobs get their pod configuration (hardware and k8s
config) to use local data, rather than using the pod-configs repo.

As pod configuration would only be stored locally on the system under test,
updating/editing it would be easier to iterate on. It would also make it easer to create/deploy new pods.

This also has security benefits, as K8s configuration and other semi-sensitive
data would no longer be be publicly shared.

Steps:

• Create and document a template for the pod configuration so new configurations
  can be created easily as new pods come online. (where should this be put?
  voltha-system-tests or ci-management). Best practice is still to create a
  local git repo that contains the configuration.

• Change Jenkins jobs to look for new pod-local configuration, and if not
  found check out the pod-configs repo as a transitional process.

• Use a naming scheme for files that includes the Jenkins executor name.

• Change Jenkins jobs to print out non-sensitive parts of the pod
  configuration, so if a job fails this information can be used to help debug
  problems. Also, the git commit hash of local config.