Simplified events draft

[SebastienGllmt]

This PR simplifies the event system, also sets up the events to use typebox so that it is both strongly typed and so that we can later export them as json-schema for documentation purposes and so that it works well with the json-schema we'll use for the log system

• doesn't solve the ENV issue
• disable external users from sending messages to the engine/batcher (I believe this can be done with this)
• add more status options to the batcher event
• don't only send block events when a block is non-empty (non-empty should maybe just be a filter on blocks?)
• fix the issue where block events may be skipped if paima engine shuts down (see Handling shutdowns in event listeners in Emit event standard for games #373)
• Disable MQTT reserved keywords (/, +, #) in event names
• test this PR

Define an event

const QuestCompletionEvent = genEvent({
  name: 'QuestCompletion',
  fields: [
    {
      name: 'questId',
      type: Type.Integer(),
      indexed: true,
    },
    {
      name: 'playerId',
      type: Type.Integer(),
    },
  ],
} as const);

Listen to Messages

Listen to an event

PaimaEventManager.Instance.subscribe(
  {
    topic: QuestCompletionEvent,
    filter: { questId: undefined }, // all quests
  },
  event => {
    console.log(`Quest ${event.questId} cleared by ${event.playerId}`);
  }
);

Send Messages

Sent an event

PaimaEventListener.Instance.sendMessage(
  QuestCompletionEvent,
  {
    questId: 5,
    playerId: 10
  }
);