chore: remove stale scripts

[bacongobbler]

Reason for Change: These scripts/Dockerfiles are either unused by CI or are not actively being maintained, so I assume these are safe to remove.

I'm not totally sure about removing the root Dockerfile, but given that there are several outdated packages in there I assumed it was also stale. Please let me know if that is not and I'm happy to restore anything that is still in active use.

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• tested upgrade from previous version

Notes:

[codecov]

Codecov Report

Merging #224 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #224   +/-   ##
=======================================
  Coverage   53.23%   53.23%           
=======================================
  Files          95       95           
  Lines       14240    14240           
=======================================
  Hits         7580     7580           
  Misses       5994     5994           
  Partials      666      666

[mboersma]

👍 This looks like cruft to me. I could never figure out where the Dockerfile might be used so left it alone out of caution, but now that we've switched over to aks-engine let's tidy up. We can always restore a file if needed.

[mboersma]

/lgtm

[acs-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bacongobbler, mboersma

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mboersma]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jackfrancis]

Do we want to add a follow up item to standardize upon a canonical docker image for aks-engine development/CI?

[bacongobbler]

Yeah that may be a nice-to-have. I'll file a ticket for that now

[mboersma]

@jackfrancis you mean other than deis/go-dev? I think we use that consistently now that this cruft is removed, but we could consider alternatives.

[jackfrancis]

@mboersma Not concretedly "instead of", as possibly "deis/go-dev" is the appropriate docker environment for aks-engine dev long-term. I think we just want to standardize that, with community input.

[bingosummer]

This PR breaks the doc: https://github.com/Azure/aks-engine/blob/master/docs/tutorials/quickstart.md#docker-development-environment. Is it expected?