Create-invite Command fix

[zuuring]

Notes

The /create-invite command was failing to appear correctly on the prod version of valkyrie. From local testing it seems like this could be the case of commands.set vs commands.create.

Also removes fjord.ts since it seems likely that was causing the main issue with overwriting commands. Especially since n8n integration hasn't been a thing except for standups.

[zuuring]

One thing discovered in testing is that even if we remove fjord.ts the old commands are stored in the cache. So quick fix is to just run a command wipe before we run the rest. Or just add it temporarily to remove set fjord.ts commands /n8n, /debug, /activity, /stale-issues, /issues

Something along these lines we could use to ensure cache is clear of other valkyrie commands

const existingCommands = await application.commands.fetch()
await Promise.all(existingCommands.map(cmd => application.commands.delete(cmd.id)))
robot.logger.info("All old commands deleted")

This then wipes the commands stored before we set the new one's in Valkyrie

The main question is if we use this route, we would need to run it before the discord-scripts are loaded, so perhaps in discord.ts

[zuuring]

Added a quick check if n8n commands exist, then if so proceed to delete all commands. We can remove this afterwards since it only has to run once to wipe old fjord.ts commands from guild cache.

[Shadowfiend]

All righty let's ship it. We'll probably want to restart once after the initial execution as well.