Convert HTO guide to business oriented example

[akeller]

@christian-konrad wanted to convert the existing HTO guide example to something more business-oriented - expense report, multi-step approval process, etc. Something relatively common and easy to follow, but starts to reveal complexity and how Camunda would handle that.

The challenge is this content is upstream from the Onboarding product experience, Academy, and possibly other areas. This means any significant change to this guide would cause the others to fall out of line.

IMO, this will happen occasionally and should be well communicated to keep use flexible and iterative if we want to make changes. Otherwise, we'll always be stuck with what we did in the past - not good.

Scope & steps, not necessarily in order:

• Commit to a business-oriented use case (expense report?)
• Define BPMN, or update existing model with new language/terminology
• Update or rewrite guide steps
• Communicate changes to Onboarding and Academy teams (preemptively and certainly after)
• Determine if all changes will be made together across areas or if there are any blockers to updating docs first

[akeller]

@christian-konrad, I added this issue to the HTO Team board, but I'll let you update the status and anything else you need.

[akeller]

@christian-konrad is this still relevant? This would be a good candidate for someone from the HTO team to pair with @christinaausley on.