feat: all users can edit "Templates" team and moveFlows to teams they're allowed to edit

[jessicamcinchak]

• I added a "Templates" team to production & staging, this change ensures any user will have teamEditor access to "Templates" by default when they're added independent of records in the team_members table (if this feels too liberal, very happy to re-think how we should do this!)
• moveFlow Editor store method now checks if the given user has permission to move the flow into the requested team. If they don't, it'll display and error and return early. The copy/move menu is only visible in teams you can edit already, so I don't think we need to do anything similar with other store methods besides moveFlow yet.

Testing:

• (If you're a platformAdmin, toggle this off first in https://hasura.2239.planx.pizza/console/login)
• I see an "edit" icon next to Templates even though I do not have a team_members entry
• Inside "Templates", I can create a flow, copy it, and move it - I can successfully move to a team that I have edit access to, but see an error message when I try to move it to a team I can only view

[DafyddLlyr]

Unfortunately, I think this approach won't work as expected.

The way I understand it to work is that Hasura will run a check against the team_members table before any actions, so if we modify the UI or even the JWT to insert a role for the templates team it should fail.

There's a few ways we could achieve this -

1. Creating a record for each user in the team_members table to give them teamEditor role for the templates team. A migration for all existing users + maybe a trigger on user creation to insert a record could work.

2. Modify the permissions check in Hasura to say "if user is team member, or team = templates"

No strong feelings either way here - I suspect option 1 is a little more robust / discoverable / expected?

[DafyddLlyr]

Ah actually I might be wrong here sorry...!

I thought it was a copy + move we needed, but I think this would work for just a move. I'm going to get a coffee... ☕ 😅

[github-actions]

Removed vultr server and associated DNS entries

[jessicamcinchak]

Next steps:

• This currently works because the underlying API routes for moving & copying aren't scoped to user permissions yet
• We'll need to update this approach once that is implemented, but we're happy to merge this in the meantime because the UI will remain consistent