quickstart.sh needs tests

The new quickstart.sh suffers from the same problem that k3d-dev does: it has no tests.

We need to have either:

1. A detailed testing plan for quickstart.sh that specifically outlines the supported use cases, how to execute them, and how to test if they were successful. This plan should be sufficiently detailed that anyone making change to the script can follow it and provide proof of testing. OR
2. An automated testing harness that performs automated testing of known supported use cases and provides assertions that such use cases remain functional after incoming changes are applied. This proof should be provided on the merge request.

Regardless of which approach is chosen, before merging any changes to quickstart.sh, we MUST acquire positive proof that the agreed upon testing procedure has been followed and all applicable use cases have been proven to pass testing.

marked this issue as related to #2494

mentioned in issue #2496 (closed)

added triage-kind label

added triage-priority label

marked this issue as related to #2518 (closed)

marked this issue as related to big-bang/pipeline-templates/pipeline-templates#622

added big-bang#472 as parent epic

@akesterson this issue has been inactive for 30 days and is being labelled as stale. If this issue is still required please take action by removing the stale label and commenting with an update, status, or justification. If this issue is not required please close it or label it as delete-me. If no action is taken this issue will be auto closed in 60 days.

added stale label