(Doc+) quickstart+KB

[stefnestor]

👋 howdy, team! This is first pass to streamline the ECK guide for common support misunderstandings. It:

1. links the sub-quickstart pages to each other to show their required order
2. updates Elasticsearch + Kibana references to their respective {es} and {kb} doc variables (this is why PR looks big)
3. links the applicable Kubernetes documentation before each console command
4. links the in/directly mentioned sister pages (requiring adding some anchors)
5. moves quickstart pages ("Use persistent storage", "Check out the samples") content in-line
6. shifts "upgrade deployment" to "update" (since example is modifying not stack version upgrading) and links previously written and common troubleshooting note about downsizing volumes

[stefnestor]

Build failed on ... which I didn't edit. I imagine something else hidden is wrong with my update if y'all would kindly assist 🙏

INFO:build_docs:asciidoctor: ERROR: operating-eck/operating-eck.asciidoc: line 12: illegal block content outside of partintro block

[barkbay]

Build failed on ... which I didn't edit. I imagine something else hidden is wrong with my update if y'all would kindly assist 🙏

Refer to my comment here: #8128 (comment)

[stefnestor]

@barkbay, thanks! The last build timed-out but I don't have Buildkite permissions to "rebuild". Would you kindly retry that? 🙏

[thbkrkr]

cloud-on-k8s-operator/build timed out, I retried it. However, docs-build-pr/build failed with:

INFO:build_docs:asciidoctor: ERROR: quickstart.asciidoc: 
  line 23: illegal block content outside of partintro block

[barkbay]

Almost LGTM, as mentioned in some of my comments my recollection is that we should avoid latinisms or the verb "to see", not sure it it are up-to-date recommendations when writing documentation though.

[stefnestor]

@barkbay latinisms are removed, cheers; any other recommendations from you or @thbkrkr?

[barkbay]

@barkbay latinisms are removed, cheers; any other recommendations from you or @thbkrkr?

I think there are still a few of them introduced in this PR (~10 via for example). As I said we used to avoid and remove them, I can't tell if we still want to apply this practice in our documentation though.

LGTM otherwise.