feat[api]: create flows from templates

[jessicamcinchak]

Changes:

• Removes redundant createFlow GraphQL mutations from the frontend store and instead calls a new API route flows/create to access existing API-side mutations already used by copy, move, etc.
• Adds another new API route /flows/create-from-template/:templateId which creates a new flow in the target team with a populated templated_from reference and data matching the source template (nodes are not renamed like on copy)
  • This route cannot be called from the frontend until we have a way of identifying & selecting "source templates" from the skeleton modal - but it's possible to call it direct from Swagger docs in the meantime by passing any valid flowId as the templateId

[github-actions]

🤖 Hasura Change Summary compared a subset of table metadata including permissions:

Updated Tables (1)

• public.flows permissions:

  	insert	select	update	delete
  api	➕/➖
  demoUser	➕/➖
  platformAdmin	➕/➖
  teamEditor	➕/➖

  4 added column permissions

  	insert	select	update
  api	➕ templated_from
  demoUser
  platformAdmin
  teamEditor

[github-actions]

Removed vultr server and associated DNS entries

[jessicamcinchak]

[Implementation] Make sure live services are always up to date (aka flows copied from Templates should receive updates)