fix: fetch & flatten the latest published version of external portal data when publishing the parent flow

[jessicamcinchak]

We're changing the rules of how we "publish" flows:

• Currently, "publishing" snapshots the draft content of the parent flow, and the draft content from each external portal (regardless of published status) into a single "published version" of that parent flow
• Now, the parent flow can only be published if each of its' external portals are also published
  • This means "publishing" now snapshots the draft of the parent flow, and the published content of each external portal
• This also introduces three unique routes for viewing your flow content in the Editor:
  1. /preview (next → /published) - the latest published version of the parent flow
     • Icon disabled and displays NotFound if not published yet
  2. /amber (next → /preview) - the draft of the parent, plus the latest published version of each external portal
     • Reflects exactly what you'll get when you click publish next
     • Displays an error warning and NotFound if any external portals are unpublished (same error as when you click "Check for changes to publish")
  3. /draft - the draft of the parent, plus the draft of each external portal
     • Useful for testing automations and content changes that cross many different flows
     • Hidden unless your user role is platformAdmin

Key code changes:

• [API & Editor] Updates dataMerged flattening logic (incl tests) in the API ONLY and removes the duplicate definition from the Editor
• [API] Adds a public GET endpoint /flow/:flowId/flatten-data (incl tests and Swagger doc) that can be called by the Editor views /amber & /draft instead of relying on the duplicate definition of dataMerged
• [API] Updates existing tests for validateAndDiff & publish to reflect new rules and error handling, and draw from consistent mock data
• [Editor] Aligns views to 'next' route names (draft, preview, published)
• [Editor] MVP simplified diff message of changes to publish and notification badges on publish button

Testing notes:

• publish succeeds when external portals are published
• publish throws a meaningful error when external portals are not published
• /published loads published flow and published external portal data
  • /preview redirects to /published
• /amber loads draft flow and published external portal data
  • /unpublished redirects to /draft
• /draft loads draft flow and draft external portal data

Future scope:

• Redirect /amber → /preview after ~30 days (will set Slack channel reminder)
• Addressing blank screens when reaching portals in the editor sidebar
• Concept of when a flow is "live"

[jessicamcinchak]

Adjust "publish" function to read from published-version of external portals, rather than live version

[github-actions]

Removed vultr server and associated DNS entries

[DafyddLlyr]

Just done a code-only review with a few small comments / nits, will test on Pizza now 👍

API testing looks solid 👌

[DafyddLlyr]

Had a good play around with this and all is working as expected on Pizza ✅

• publish succeeds when external portals are published
• publish throws a meaningful error when external portals are not published
• /preview loads published flow and published external portal data
• /publish-preview loads draft flow and published external portal data
• /unpublished loads draft flow and draft external portal data

[DafyddLlyr]

Changes look good thanks!

[DafyddLlyr]

Reviewed routing changes ✅