Support multiple routes in the same file

[Delawen]

Context

Sometimes files contain more than one route. The front end right now is not considering a second route that may be available on the same file.

We may need a dropdown with the list of routes in the file. But then, the source code we see will not be the complete list of routes. Or would it?

Roadmap

• Create a new store that handles multiple flows (chore: Create new FlowsStore that supports multiple routes #1748)
• Add flows identifiers to individual flows and steps (chore: Add id and integrationId properties #1727)
• Add initial support for multiple flows (feat(multiple-flows): Enable experimental support for multiple flows #1749)
• Support editing steps (feat: Support editing steps from multiple flows #1770)
• Wire up new backend endpoints (feat/wire-up new backend endpoints to support multiple flows #1823)
• Bug: Opening a similar step brings previous information (feat/wire-up new backend endpoints to support multiple flows #1823)
• Delete all flows (chore: Add delete all flows functionality #1763)
• Remove previous IntegrationJSONStore (chore: Remove IntegrationJSONStore #1835)
• Create a new flow (Feat/add new flow #1870)
• Flows interaction (feat(flows): Add mechanism to navigate between flows #1880)
  • List all flows
  • Delete a flow
  • Being able to hide/collapse flows
• Review remaining methods and ensure tests cover everything
  • fix(viz): Avoid rerendering of VisualizationStepViews #1901
  • chore(settings): Remove deprecated fields #1903

Associated bugs

• When deleting all routes, the last one stays in the code editor  #1911
• When using kaoto code editor for editing multiple routes - after sync only first route stays displayed #1910
• Showing/Hiding and Deleting the Route - the dropdown is hiding #1896
• Multiflow Routes counter - showing incorrect information #1894

Examples

Example of a single route

- from:
    uri: "timer:yaml"
    parameters:
      period: "1000"
    steps:
      - set-body:
          constant: "Hello Camel K from yaml"
      - to: "log:info"

Example of multiple routes

- from:
    uri: "timer:yaml"
    parameters:
      period: "1000"
    steps:
      - set-body:
          constant: "Hello Camel K from yaml"
      - to: "log:info"
- from:
    uri: "timer:anotherone"
    parameters:
      period: "50000"
    steps:
      - set-body:
          constant: "Nobody expects the second route!"
      - to: "log:info"

[brunoNetId]

I think this is a must.
it helps organised code and improve readability

[rstroop]

Most of the Camel I write has multiple routes. I'd like to add that if we create directs it would be nice to have a dotted line between those routes showing their connection.

[lordrip]

Related issue KaotoIO/kaoto-backend#634