Enable full support for inbound gateway nodes

[a-asaad]

Motivation and Context

Treating inbound gateway nodes the same as standard request-reply nodes was leading to issues with diagram UX, the resulting flows were not intuitive since the inbound gateways forced the flow to loop back around to the origin, leading to diagrams that were difficult to work with.

This PR introduces the concept of a "follower" node, allowing the inbound gateway's reply channel to be represented as a separate node, maintaining a clean left-to-right (or top-to-bottom) flow.

Details

• Add a new inbound_request_reply connectionType to the EIP JSON schemas
• Update the XSD parser to categorize inbound gateway components with the inbound_request_reply connectionType
• Update the flow translator to support inbound_request_reply components
• Add support for follower node types in the flow diagram. Make use of follower nodes for inbound gateways.

Screenshots (if appropriate)

Before

After

Checklist

• The PR follows the branch and commit styles outlined in the CONTRIBUTING doc
• (UI changes only) Linting and formatting checks pass locally with the new changes (npm run precommit from the ui directory)