Review the whole Kogito Serverless Workflow Guides documentation to be the new SonataFlow Documentation.

The docs must reflect our strategy, given that:

• This will be the initial Sonata Flow website.

• Developers can pick their experience:
  1. A "raw" workflow project, where developers can develop their workflows without any Java/Quarkus previous knowledge. Our tooling (CLI and operator) hides the build process and application execution.
  2. A quarkus workflow project, which is the traditional Quarkus Maven project with the Sonata Flow Extension. Users have more control over their projects and how they build workflows. Can add custom Java code, integrate with other libraries, and so on.

The documentation must reflect these two experiences. So when writing a guide or adding a new section, bear in mind that. Overall when talking about workflow execution, we can point to a section explaining how to do it based on the experience the user chose.

See also: https://docs.google.com/document/d/163zuhGNnYDrqRdi3j4NpNKliLsKp8M5Z1gRoYUEGiOw/edit