Create proper toast mechanism

[aggregate1166877]

Details:
The current toast implementation was thrown together in a quick/dirty fashion (in literally 10 minutes) and has multiple issues (the most important one being that queuing messages does not work, and likely never will).

Task:
Implement a new toast system utilising the newly implemented React core. Delete the old toast mechanism.

We need multiple toast types:

• System messages (messages floating in the center of the screen for a bit),
• Quest messages (larger messages with headers briefly floating at the top, indicating game status change).
• Interaction messages (such as 'Press [E] to activate door.').
• Notifications (messages in top right; they have exit buttons and may have headers).

Not all of them will be made equally - for example, system messages may recur for things like "Maintenance at 18:00." Interaction messages have no time limit, and are instead killed by a deletion event. Quest messages will have no option to be displayed indefinitely, and will have 'long' or 'short' time limits.

Toast messages should have the option to grab input priority for potential interaction. For example, a quest message might be displayed for 5 seconds, and have a little 'Press [Tab] to open journal' note that takes one to that particular entry in the journal. A 'Press [E] to interact' should have appropriate callback mechanisms.