Add move action

[3mcd]

This PR adds a simple move action that moves pubs between stages.

The moves are immedately reflected (when run manually) in the UI. This was accomplished by adding a revalidateTag call in the actions framework code.

This PR also adds a fourth stageId parameter to the action run functions. This will allow actions to do work in the context of their stage. In this case, the stageId parameter is used to remove the pub from the stage where the action was run.

Issue(s) Resolved

Resolves #339

Test Plan

• Open the stage editor page
• Add the move action to a stage. Configure the action instance with the stage id of the stage you plan to move pubs into.
• Create a pub or two in the stage.
• Run the action manually on pub(s) you created. The pub should move into the new stage and the change should be immediately visible without a refresh.

[qweliant]

Adding some indication its the id here would be nice

[3mcd]

Good call. I think I'll skip updating the description for now because we'll need to provide a custom dropdown that populates with the community's stages. But I can add a comment.

[kalilsn]

I think this is movePub query is a good candidate for being extracted to a kysely helpers module (or just an existing lib/server module) since there are so many ways to do it, and one of them (updating rather than insert+delete) breaks our event listener.

Separately, do you know how doing these queries in a transaction compares to doing them in a CTE? Is it still a single request/response if you use a transaction?

[3mcd]

I doubt it treats two operations any differently other than rolling them back in the event of an error, so its probably opening two "connections". I'm actually not sure if a CTE would be rolled back within a transaction. And furthermore I'm not sure if doing a destructive operation within a CTE is a good pattern or not just to save a round trip. It was my understanding that CTEs are mostly used for generating read-only views (e.g. in the case of a recursive query) used by the outer/primary portion of a query.

I'll pull the query out into a kysely helper.

[kalilsn]

Just added the cte change per our slack convo! Feel free to extract it but we can also do that later.

I also tested it out and it works well! I do think we should change the stage selection from a string to a list of stages by name, but there's a lot of ways we could do that so I can see why you'd want to wait on that. just saw your comment lol