CSI image version and deployment manifests updates

[dkoshkin]

Is this a bug fix or adding new feature?
Fixes #158

What is this PR about? / Why do we need it?
This PR replaces the deprecated https://github.com/kubernetes-csi/driver-registrar with:

• cluster-driver-registrar: https://github.com/kubernetes-csi/cluster-driver-registrar
• node-driver-registrar: https://github.com/kubernetes-csi/node-driver-registrar

---

• Because the driver-registrar is now replaced with 2 different images one cluster-driver-registrar and one node-driver-registrar it no longer makes sense to have both of those pods in the csi-node DS as node-driver-registrar is a cluster level component and should register the driver once, ie in a single pod.
  To support this, this PR also merged the attacher.yaml and provisioner.yaml into a single controller.yaml StatefulSet (this is also consistent how other CSI drivers including DOs and GCPs does it)
  I also went through all the RBAC policies and tested them to confirm there aren't any extra/missing ones.
• Replaced quay.io/k8scsi/csi-attacher:v1.0-canary and external-provisioner images with a stable latest release v1.0.1 - having version predictability is always good - Interested on everyone else's thoughts on this.
• Set priorityClassName which requires the pods to run in kube-system namespace.
• I also removed directories for versions pre v1.13, Kubernetes v1.13 uses CSI 1.0 and although this driver has a release https://github.com/kubernetes-sigs/aws-ebs-csi-driver/releases with support for CSI 0.3, that release has some bugs and users can still use that version for older k8s versions but they should be encouraged to use newer, more stable versions. - Interested on everyone else's thoughts on this.
• Added double quotes to the secret.yaml file, this allows users to rely on EC2 instance roles and still run kubectl apply -f without having to remove that file.

What testing is done?
Locally ran e2e and sanity tests.

[k8s-ci-robot]

Hi @dkoshkin. Thanks for your PR.

I'm waiting for a kubernetes-sigs or kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[leakingtapan]

/ok-to-test

[coveralls]

Pull Request Test Coverage Report for Build 337

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 50.931%

---

Totals
Change from base Build 323:	0.0%
Covered Lines:	602
Relevant Lines:	1182

---

💛 - Coveralls

[leakingtapan]

/retest

[leakingtapan]

There are a lot of details here, will do another around of review

[dkoshkin]

Ok @leakingtapan I think this is ready for a final review.
New changes:

• Added double quotes to the secret.yaml file, this allows users to rely on EC2 instance roles and still run kubectl apply -f without having to remove that file.

[leakingtapan]

Thx for the quick turn around. Minor comment

[leakingtapan]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dkoshkin, leakingtapan

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 [leakingtapan]

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