fix full user object being exposed

Include full AJV error on api

Reorganise schemas a little bit

Try to fix sending messages with discord-go

Clean up array extensions

Add dotnet-ish Random class

Drop dependency on missing-native-js-functions

Fix ignored request schemas

Log schema name on error

Drop @sentry/node (Sentry support) - untested and unused

Maybe this tie

Include attachments

More relations

Actually set the referenced_message relation on new messages

Make cloud uploads work

Logging of empty messages

meow???

Log validation errors

Try to handle new attachment style in message handler

Add first half of cloud attachment uploads

Merge pull request #1305 from ZaneH/feat/handle-github-webhook ...

Implement GitHub-compatible webhook

Fix typeorm queries no longer allowing empty where clauses

Refactor `/github` endpoint into it's own file

Add OP to message.mentions when replied to ...

The `message.message_reference` stores:

1. `message_id`
2. `channel_id`
3. `guild_id`

We use the `message_id` and `channel_id` to `.findOne(...)` Message, and
find the author. If the author is the same as OP, we skip (so replying
to yourself doesn't add you to the mentions array) otherwise, it adds
the author_id to the mentions array.

Resolves: #1247

Preserve reactions when a message is edited ...

Resolves #1241

Properly filter existing embed links ...

In a previous PR, I was checking if the `.url` property existed, the
correct fix is to remove any embed that isn't a rich embed
type (non-link).

See also: #1296

Start fresh when updating embeds for links ...

In a previous commit I was attempting to be clever by only
replacing/removing embeds if necessary. This not only made the logic
more confusing but introduced a bug that would allow for orphaned
embeds when updating the search params of a URL.

This commit will remove all embeds that have a `.url` property and start
fresh. This simplifies the code and eliminates the aforementioned bug.

Fix various issues with embeds on message updates ...

The `postHandleMessage` function is parsing links and adding them to the
EmbedCache table if necessary. In the previous implementation, message
updates would push to the embeds unconditionally.

This commit parses links from the message and:

1. Normalizes the URLs
  - Useful for deduplicating similar URLs
2. Remove embeds with matching normalized URLs
  - Leaves all embeds except for ones with a `.url` property matching
  the updated message
  - This allows embeds to be re-ordered if the URL is moved
3. If no normalized URLs are found, remove all embeds
4. Take the deduplicated + normalized URLs and add an embed to the message and
insert into the EmbedCache table (if necessary)

This enables:

1. Embeds to be re-ordered by re-ordering links
2. Embeds to be removed by removing links

and fixes:

1. Duplicate embeds being attached to a message when edited

delete the null eater

acatually fix the embed issue ...

This one added the line in the right spot, sorry about the previous one lol