feat(quickstarts/tour): add Cryostat guided tour and various QuickStarts

[maxcao13]

Welcome to Cryostat! 👋

Before contributing, make sure you have:

• Read the contributing guidelines
• Linked a relevant issue which this PR resolves
• Linked any other relevant issues, PR's, or documentation, if any
• Resolved all conflicts, if any
• Rebased your branch PR on top of the latest upstream main branch
• Attached at least one of the following labels to the PR: [chore, ci, docs, feat, fix, test]
• Signed the last commit: git commit --amend --signoff

---

Fixes: #902
Closes: #880

Description of the change:

Adds a guided tour to Cryostat, similar to what Openshift does and adds 4? new quickstarts. These quickstarts and guide can be found under the (?) help button.

How to manually test:

Run normally and try each of these components out.

[github-actions]

Test image available:

CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-web:pr-910-ebcac8b83c9efddc36968d6f8fa91b54447ed325 sh smoketest.sh

[maxcao13]

Should be ready for light review, settings quickstart could use extra work, and dashboard quick start has been started yet.

[github-actions]

Test image available:

CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-web:pr-910-ce3cb9dd1af306391b8ec90bdc84d90f11d51448 sh smoketest.sh

[andrewazores]

Awesome. The tour currently misses Automated Rules and Events nav items, I think those should be covered too. Events should be pretty brief to summarize, and Automated Rules doesn't need too much explanation here since there is also a quickstart for it that explains it in depth (also nice).

[tthvo]

Looks amazing! I am blown away :D Just a notice that some references to an element is not working (maybe the element is lacking the data-highlight props). For example, the event template selector in Automated Rules. We might also have to check collapsed navigation sidecar and actions overflow button in Recording table.

[github-actions]

Test image available:

CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-web:pr-910-166eca6b76f7037b1f79b7e75ccaafed8f8ee538 sh smoketest.sh

[github-actions]

Test image available:

CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-web:pr-910-d2c0ad1d4a7c7371d2a871f5e67027c00af691e5 sh smoketest.sh

[github-actions]

Test image available:

CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-web:pr-910-b932b3e91c67caf51ab214f4b7403e73b0ec14da sh smoketest.sh

[andrewazores]

allow you start recordings on a target JVM

I think this should be pluralized: "allow you to start recordings on target JVMs based on sets of conditions"

Any particular reason for calling out reports here? Reports can also be generated on the Recordings and Dashboards views, after all.

The Events page lists the Event Templates that Cryostat can currently apply to a JFR recording. It also lists Event Types that are available on the target JVM.

"The Events page lists the Event Templates that can be used for creating Flight Recordings. It also details the JFR Event Types that can be recorded within each target JVM."

[github-actions]

Test image available:

CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-web:pr-910-81924c2488bae5db2eabe339addf33095d4d4e26 sh smoketest.sh

[github-actions]

Test image available:

CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-web:pr-910-96799e6d196bd08adbeb46b862223228cc9ba83b sh smoketest.sh

[tthvo]

Implementations and contents look good to me! Leaving to Andrew for finalizing contents :))

[andrewazores]

One last little nitpick: please remove mentions of the word "upstream", and wherever this is referring to some URL, please ensure that URL is provided by the build.json file rather than hardcoded into the sources.

[github-actions]

Test image available:

CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-web:pr-910-407aa17ecb01a6db097824580d407931318e6e3f sh smoketest.sh

[github-actions]

Test image available:

CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-web:pr-910-57b9b46935fbce785ab41fda52d1c4aa1c4444fd sh smoketest.sh