EKS self managed node group support

[richardcase]

/kind feature

Describe the solution you'd like
When creating an EKS cluster i want to provision a "self managed node group" that uses an EC2 instance for worker nodes. Will need to use the boostrap data from #1779.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Cluster-api-provider-aws version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[rudoi]

Could this and #1785 be solved by implementing MachinePool providers (maybe even #1786 if we're willing to flex the definition of "machine pool")?

"AWSMachinePool", for example, could map to an AutoScalingGroup
"AWSManagedMachinePool" (or even just "AWSManagedNodeGroup", names are hard) could map to a Managed Node Group.

I've worked very little with Fargate profiles so I'm not quite sure how that would go at present.

[rudoi]

/assign @mytunguyen
/assign @nicoleyson

[k8s-ci-robot]

@rudoi: GitHub didn't allow me to assign the following users: mytunguyen.

Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @mytunguyen
/assign @nicoleyson

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.

[nicoleyson]

/assign @mytunguyen

[randomvariable]

@mytunguyen is there anything left to do on this given the bootstrap provider being added?