Cloud Native should NOT be a category

[kostis-codefresh]

Cloud native is a characteristic/trait. It doesn't make sense to have a category, because then 90% of the other cards should also be here.

It also gives the false impression that tools that are not there are "not" cloud native.

Isn't Tekton cloud native?
Isn't ArgoCD cloud native?
Isn't Shipwright cloud native?

The current contents of this "category" are unrelated. Terraform is a CLI that implements infrastructure as code, Rancher is a cluster orchestration/management platform, Alibaba is a whole cloud provider, while Ketch is an application for Kubernetes deployments.

Related to #175

[sbtaylor15]

Point to the CNCF landscape as a embedded landscape link. This will enable us to have the CNCF maintain the landscape for this category.

[MarckK]

TODO:
Make all one Infrastructure Deployments -- remove subcategories.

Puppet will likely move out to Config Management, see #185

All Infrastructure Deployments - Cloud Native will then be in category Infrastructure Deployments, with no specification around Cloud Native, which will be removed (with the implication that other tools are not CN).

[MarckK]

Closing as remaining work to be done is surfaced in #208.