CCM-13675: Event code generation improvements

[simonlabarere]

Description

Generation of guard functions to assist in reducing boiler plate code and avoiding type casting. The behaviour of the whole app should remain unchanged with the exception of the normalisation of some logs.

Example of a generated guard function:

export function validateMESHInboxMessageDownloaded(
  event: unknown,
  logger: Logger,
): asserts event is MESHInboxMessageDownloaded {
  if (!eventMESHInboxMessageDownloadedValidator(event)) {
    logger.error({
      err: eventMESHInboxMessageDownloadedValidator.errors,
      description: 'Error parsing MESHInboxMessageDownloaded event',
    });
    throw new InvalidEvent(eventMESHInboxMessageDownloadedValidator.errors);
  }
}

Which can be used like this:

const event: any = getSomeEvent();

validateMESHInboxMessageDownloaded(event, logger);

// event is now detected with a type of MESHInboxMessageDownloaded without any casting

Type of changes

• Refactoring (non-breaking change)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would change existing functionality)
• Bug fix (non-breaking change which fixes an issue)

Checklist

• I am familiar with the contributing guidelines
• I have followed the code style of the project
• I have added tests to cover my changes
• I have updated the documentation accordingly
• This PR is a result of pair or mob programming
• If I have used the 'skip-trivy-package' label I have done so responsibly and in the knowledge that this is being fixed as part of a separate ticket/PR.

---

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

• I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

[Ian-Hodges]

I'm liking it. Just the one comment about an error log potentially triggering duplicate alarms.