feat: Clarify NIC install & upgrade steps

This commit makes a number of changes to clarify what the precise steps
are to install, upgrade and uninstall NGINX Ingress Controller

- The Install document clarifies necessary steps
- Uninstall steps have been moved to the bottom of the document
- Upgrade instructions have been moved into their own document

The changes made focused on clarifying the critical path for one single
user story, as lots of unnecessary contextual information was being
provided, which was causing confusion.

With this commit, the general reading and execution flow for these
deployment steps become more coherent. Similar changes may be made for
Manifests documentation, if common steps are identified.

Author: ADubhlaoich

content/nic/installation/ingress-nginx.md

@@ -1,12 +1,10 @@
 ---
-nd-docs: DOCS-1469
-doctypes:
-- tutorial
-tags:
-- docs
 title: Migrate from Ingress-NGINX Controller to NGINX Ingress Controller
 toc: true
-weight: 500
+weight: 700
+nd-content-type: how-to
+nd-product: NIC
+nd-docs: DOCS-1469
 ---
 
 This document describes how to migrate from the community-maintained Ingress-NGINX Controller to F5 NGINX Ingress Controller.

content/nic/installation/installing-nic/installation-with-helm.md

@@ -2,8 +2,8 @@
 title: Installation with Manifests
 toc: true
 weight: 200
-type: how-to
-product: NIC
+nd-content-type: how-to
+nd-product: NIC
 nd-docs: DOCS-603
 ---
 

content/nic/installation/installing-nic/installation-with-manifests.md

@@ -1,6 +1,6 @@
 ---
 title: Integrations
 description:
-weight: 600
+weight: 800
 url: /nginx-ingress-controller/installation/integrations
 ---

content/nic/installation/installing-nic/upgrade-to-v4.md

@@ -1,10 +1,10 @@
 ---
-nd-docs: DOCS-606
-doctypes:
-- ''
 title: Run multiple NGINX Ingress Controllers
 toc: true
-weight: 400
+weight: 600
+nd-content-type: how-to
+nd-product: NIC
+nd-docs: DOCS-606
 ---
 
 This document describes how to run multiple F5 NGINX Ingress Controller instances.
@@ -17,8 +17,6 @@ It explains the following topics:
 
 {{< note >}} This document refers to [Ingress]({{< ref "/nic/configuration/ingress-resources/basic-configuration.md" >}}), [VirtualServer]({{< ref "/nic/configuration/virtualserver-and-virtualserverroute-resources.md#virtualserver-specification" >}}), [VirtualServerRoute]({{< ref "/nic/configuration/virtualserver-and-virtualserverroute-resources.md#virtualserverroute-specification" >}}), and [TransportServer]({{< ref "/nic/configuration/transportserver-resource.md" >}}) resources as "configuration resources".{{< /note >}}
 
----
-
 ## Ingress class
 
 The [IngressClass](https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-class) resource allows for multiple Ingress Controller to operate in the same cluster. It also allow developers to select which Ingress Controller implementation to use for their Ingress resource.
@@ -35,16 +33,12 @@ The default Ingress class of NGINX Ingress Controller is `nginx`, which means th
 {{< note >}}- If the class of an Ingress resource is not set, Kubernetes will set it to the class of the default Ingress Controller. To make the Ingress Controller the default one, the `ingressclass.kubernetes.io/is-default-class` property must be set on the IngressClass resource. To learn more, see Step 3 *Create an IngressClass resource* of the [Create Common Resources]({{< ref "/nic/installation/installing-nic/installation-with-manifests.md#create-common-resources" >}}) section.
 - For VirtualServer, VirtualServerRoute, Policy and TransportServer resources, NGINX Ingress Controller will always handle resources with an empty class.{{< /note >}}
 
----
-
 ## Run NGINX Ingress Controller and another Ingress Controller
 
 It is possible to run NGINX Ingress Controller and an Ingress Controller for another load balancer in the same cluster. This is often the case if you create your cluster through a cloud provider's managed Kubernetes service that by default might include the Ingress Controller for the HTTP load balancer of the cloud provider, and you want to use NGINX Ingress Controller.
 
 To make sure that NGINX Ingress Controller handles specific configuration resources, update those resources with the class set to the value that is configured in NGINX Ingress Controller. By default, this is `nginx`.
 
----
-
 ## Run multiple NGINX Ingress Controllers
 
 When running NGINX Ingress Controller, you have the following options with regards to which configuration resources it handles: