### Notes
This adds an additional feature to the new audit channel flow. Once an `ext-name-audit` channel is setup, now you can make an `int-name-audit` channel, which will perform these steps:

1. Setup a new role `Defense Internal: Name`
2. Generate an invite for the `int-name-audit` channel
3. Check if a matching `ext-name-audit` channel exists, if so assign `ViewChannel` permission to `Defense Internal: name` role.

This is still a work in progress just testing out the ability of assigning a role to an invite based of the uses it has.

Rewrite some of the checks and counts in-order to correctly match the role. The previous method was breaking on different format channels such as `ext-thesis-test-audit`

Moves `listInvites` into it's own function for easier calls

Refactor the `guildMemberAdd` event to resolve lint expression errors and make sure channel name is found correctly based on ext, int patterns

Resolves the issue that would fail to assign internal roles to external channel if the channel name had the format `ext-client-name-audit` vs `ext-clientname-audit`

This fixes the bug happening on invites not counting correctly if they were being used more than 2 times on certain edge cases.

This is still WIP but adds the `defense-audit` command with the parameter `client-name` to automatically build `int-clientname-audit` and `ext-clientname-audit` channels with two roles `Defense Internal: ClientName` and `Defense External: ClientName`.

Can only be run from the `defense` category

This commit makes it so the `defense-audit` command can only be run within the `defense` parent category of channels and will send a reply if it isn't working as it should.

Also adds an `interaction.editReply` inorder to avoid any timeout issues happening

Removes the debug loggers from the scripts, not needed anymore!

This commit adds a number of changes to the audit channel flow. mainly:

- Update permissions if channel already exists
- Check if role already exists, if so skip
- Changed logic so that if audit channels already exist, we output a different message to interaction
- Remove embeds by wrapping invite URL in quotes.
- Change verbiage around messages
- Separates InternalChannel and externalChannel
- Changed invite code permission match

This commit switches over from discordjs `Collection` in favour of storing invites as an object.

This commit does some refactoring based off review feedback (thank you!) as well as making sure the invite uses / expiry date is listed properly.