Passed a JWT with to a cluster with a 'cluster' role.

[hahnd]

Added a new API Action to delete a cluster. Cluster uses the JWT to call the API to shutdown when it is finished, rather than trying to delete its own stack.

Expected Differences

• [ ] Do these changes modify the system output in any way? [Yes or No]
  If yes, please describe:
  

Pull Request Testing

• [ ] Describe testing already performed for these changes:
  

• [ ] Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  

• [ ] Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes or No]

• [ ] Do these changes include sufficient testing updates? [Yes or No]

• [ ] Will this PR result in changes to the test suite? [Yes or No]
  If yes, describe the new output and/or changes to the existing output:
  

• [ ] Please complete this pull request review by [Fill in date].
  

Pull Request Checklist

• [ ] Review the source issue metadata (labels, project, and milestone).
• [ ] Complete the PR definition above.
• [ ] Ensure the PR title matches the feature or bugfix branch name.
• [ ] Define the PR metadata, as permissions allow. Select: Reviewer(s) Select: Project Select: Milestone as the version that will include these changes Select: Development to link to the original development issue.
• [ ] After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• [ ] Close the linked issue and delete your feature or bugfix branch from GitHub.

[hahnd]

@georgemccabe - Without the JWT, the API request to delete the cluster will fail. So, unless you go out of your way to create the JWT and make it available on the cluster, the delete request will fail because it does not have the cluster ID and will not pass authentication or authorization.

[hahnd]

closes #125