Small fixes for tags

Now it correctly scales for both desktop and mobile.

The table is difficult to see on mobile but very useful on desktop,
so we change the default values depending on the platform.

Task list improvements on mobile devices

The actual .env should not be part of the repository to prevent any
secrets to be stored in git.

Remove dotenv file from git

Improve mention resolution

Pinning to the channel is not silent and we don't want that.
So instead we now save the task link in the topic using the delimiter /-/

Change pin behavior and resolve channel names in archive

It is mandatory to create an archive first before deleting the CTF.
This prevents data loss and the resulting task can always be deleted manually.
The archive command will now not delete the channels anymore.

Finishing of the commands will now be reflected in the bot reply.

Add `/delete` to delete Discord CTF integration

Now they will be properly rendered by Hedgedoc

When the note content is too big, it will be split in multiple pads.
But these pads won't be visible in the export.
This is now fixed by recursively fetch all tasks by matching the pad url.

Discord archive: image handling and recursive pad export

Otherwise this will result in errors.

Subtask export: cyclic references and uploads exclusion

In the end, it was not used but still a good feature to have for this component.

Now all the capabilities and limitations of the bot are documented in the README.

Discord: privilege change sync and better documentation

Copy of 8efa9ba
but this one is upstream included in TFNS#217.

Remove GHCR authentication notice in README

Update Hedgedoc to 1.9.9

Parsing challenges from https://angstromctf.com/

Angstromparser downstream

Updates all dependencies, resolving potential vulnerabilities.

One day they woke me up -
So I could live forever.
It's such a shame the same
Will never happen to you.

Upgrade to yarn v3 and commit all dependencies so npmjs downtime
does not cause troubles with building CTFNote.

Upgrade dependencies - September 2023

Git has added some crlfs to the file which causes the hashes to change.
This prevents booting CTFNote due to annoying restrictions in the migration script.
We revert to the old files so nobody has to change the hashes in the database.

Git is messing up the files...

Now the on it status is based on an 'active' boolean in the database and thus
we can track the history of the on it status.
This way you know who worked on it in the past but that person is not actively working on it right now.

By holding the on it button it is now possible to cancel working on it and
this will permanently remove your name from the task.

Discord messages are updated accordingly.

On it history

Otherwise a false message is send that you cancelled the task but
you didn't start the task previously.
Of course this can still be triggered by just calling the API, but this is not a security issue.

Only allow cancel if worked on task

Now you can import users based on their interest on a Discord event link from your server.
The link will be remembered but you have to press the sync button yourself to trigger the sync.

For now it only imports users. It won't remove them if they stop showing interest.

Only friends and guest will loose their role if they don't show their interest anymore.
Therefore you should not sync when someone should have access but have not
shown their interest in the Discord event, because that person will loose their permissions.

Discord event link user import

Otherwise everyone without Discord linked will be removed from the CTF.

Don't change CTF permissions when Discord is not linked

With the new on it history, the current state was not correctly detected.
The column 'active' should be taken into account when switching the on it status.

The message that indicates that it is deleted successfully can be send to a channel that already got deleted.
Therefore the editReply will fail, but now we handle it silently so it won't crash the server.

Downstream PR from TFNS#232.
Slightly changed the README for better copy paste.

Merge docker-compose.prebuild.yml into docker-compose.yml

Prevent duplicate browser notifications with multiple open tabs

The public API was extended with more categories, so we have to include them here too.

Extend HTB parser categories

API needs to wait for the database to be up before starting.

We do not know how long it takes: just because the container is started doesn't
mean that Postgres is ready. The workaround is to use a small script (start.sh)
that waits until a connection to the database can be done before passing the
execution to yarn.

The Dockerfile contains hardcoded values for the database's hostname and ports,
but there is no guarantee that these values are always the same. This is
especially true when trying to deploy CTFNote with a previously-existing
database.

This commit removes the hardcoded values and replaces them with DB_HOST/DB_PORT.

Upstream commit: TFNS@9606303

API: honour DB_HOST and DB_PORT

Force TaskBtnGroup to be in a 2x2 grid on table task display

Fixes #71

Don't include empty Discord chats in archive

… TaskBadge to task switcher