[WIP - NO MERGE] Moves subscription ID to a ENV variable on the Pipeline and a fast fail check if not set.

[cicorias]

This adds a step in the pipeline to verify if the Azure Subscription endpoint is set as a Env variable. This removes the need to add the Subscription ID at Generate time in cookie cutter.

This is based off of the YAML support branch as well.

Ideally, and will add another work item - this should be encapsulated into a vsts task - as the following code "could" be added - but if these were tasks and installable better encpasulation and reuse.

echo "calling DevOps REST API"

body=$(curl --request GET \
  --url $SYSTEM_TEAMFOUNDATIONCOLLECTIONURI/$SYSTEM_TEAMPROJECT/_apis/serviceendpoint/endpoints/$endpointId?api-version=5.0-preview.2 \
  --header "Authorization: Bearer ${SYSTEM_ACCESSTOKEN}" \
  --header 'cache-control: no-cache')

echo $body

echo "parsing json"

result=$(echo $body | jq ". |  select( .id | test(\"^${endpointId}$\"; \"i\")) ")

echo "checking result"
if [ -z "$result" ]; then
    echo 'not found'
    exit 1
else
    echo $result
    exit 0
fi

closes: https://tigna.visualstudio.com/TIEM_Welding_ML_Pilot/_workitems/edit/277/

All Submissions:

• [x] Have you followed the guidelines in our Contributing document?

• [x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

• [x] Does your PR follow our Code of Conduct?

• [x] Have you added an explanation of what your changes do and why you'd like us to include them?

• [x] Does each method or function "do one thing well"? Reviewers may recommend methods be split up for maintainability and testability.

• [x] Is this code designed to be testable?

• [x] Is the code documented well?

• [x] Does your submission pass existing tests (or update existing tests with documentation regarding the change)?

• [x] Have you added tests to cover your changes?

• [x] Have you linted your code prior to submission?

• [x] Have you updated the documentation and README?

• [x] Is PII treated correctly? In particular, make sure the code is not logging objects or strings that might contain PII (e.g. request headers).

• [x] Have secrets been stripped before committing?

[sayar]

@cicorias can you please rebase against master? It's hard to see the diff at the moment against master.

[cicorias]

this is bsaed off the yaml-pipeline-switch - so, best to await that merge. @sayar