Restructure "Serving component" section

[RichieEscarez]

Align content with the developer flow and arrange content into logical sections.

View proposed nav structure

• For all moved or renamed files, add a redirect to that file's frontmatter (Ensure that all content affected by the nav changes gets a "redirect" #1925)
• Add ‘kn’ CLI to the Getting Started
• Create a Serving only install section
• Create new “Deploying apps” section
• Organize “Scaling” content into new section
• Organize “Networking” content into new section
• Organize “Debugging (and Observabiltiy)” content into new section
• Create new “Serving concepts” section

[knative-housekeeping-robot]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh by adding the comment /remove-lifecycle stale.
Stale issues rot after an additional 30 days of inactivity and eventually close.
If this issue is safe to close now please do so by adding the comment /close.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/lifecycle stale

[abrennan89]

@carieshmarie I think each of the checkbox items on this issue could probably be an epic of its own instead, with its own subtasks. Otherwise the scope is too overwhelming I think 🙂

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen.Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen.Mark the issue as
fresh by adding the comment /remove-lifecycle stale.