move Kubeflow on AWS to legacy distributions

[thesuperzapper]

As indicated by AWS in this thread awslabs/kubeflow-manifests#794, the Kubeflow on AWS distribution is no longer actively maintained.

This PR updates the "installing kubeflow" table to reflect this fact.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: thesuperzapper
Once this PR has been reviewed and has the lgtm label, please assign 8bitmp3 for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• content/en/docs/started/OWNERS

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

[thesuperzapper]

@surajkota if you can confirm the Kubeflow on AWS distribution is no longer maintained then @zijianjoy can you please merge this PR.

This is important to avoid confusion for new users who are using AWS, to prevent them from adopting an inactive distribution.

[thesuperzapper]

@jbottum @zijianjoy I have separated the style changes that were in this PR into a separate one #3643 (which I think we should merge, as they help new users).

This PR is not only for moving AWS to legacy, so will allow us to give AWS more time to confirm if they plan to continue supporting their distribution.

[jbottum]

@thesuperzapper I think we need to consider that the last AWS release was for 1.7 and has a date of Sept 23 per this link, https://github.com/awslabs/kubeflow-manifests/releases, which I believe is within the 6 month window that you have defined as an active distribution.

[andreyvelich]

/hold due to #3693