Add script functions for reporting Kubernetes manifests from scripts

[APErebus]

Adds new functions to both the PowerShell and Bash bootstrap scripts to allow for reporting of kubernetes manifests.

There are two functions

1. Report-KubernetesManifest/report_kubernetes_manifest which takes two parameters, the manifest content and optionally, the namespace.

This function splits the manifest on --- (with/without trailing spaces) and registers each document separately using the service message.

If a manifest contains multiple documents and a namespace is provided, all reported manifests get the same namespace

2. Report-KubernetesManifestFile/report_kubernetes_manifest_file which takes two parameters, the full path to the manifest file and optionally, the namespace.

This function reads the contents of the file and then calls the function above.

[eddymoulton]

Changes look good to me, just a few nits for your consideration.

Love to see the testing - it's got me wondering if we should add tests for some of the poorly crafted yaml scenarios you identified in the PR description (eg. extra spaces before document separators, excess newlines, double document separators without content between, etc.).
I'd be content knowing you've tested these manually if you think adding them as test cases is overkill.

[eddymoulton]

Using Heredoc can clean up those escapes (disclaimer, I didn't test this)

read -r -d '' manifest << EOM
"apiVersion": "v1"
"kind": "Namespace"
"metadata":
  "name": "example"
"labels":
    "name": "example"
---    
"apiVersion": "v1"
"kind": "Namespace"
"metadata":
  "name": "diffs"
"labels":
    "name": "diffs"
EOM

[eddymoulton]

naming nit since it's not an index

Suggested change

	for i in "${MANIFESTS[@]}"; do
	for manifest in "${MANIFESTS[@]}"; do

[eddymoulton]

nit for next time: consider applying the formatting in a separate commit before the change

[APErebus]

yeah, I didn't mean to re-format but it did it :shakes-fist: