Logging Extension Improvements

Nobody has claimed this yet.

## Suggestion

- should include a global logger for use outside of the application so that we can make sure to catch and log exceptions for problems with the application boot-up. `console.log` won't cut it here as logs still need to be `json` structured and sent to an external logging service.

- Http Access Logs should be json structured rather than putting the log in string format.

## Use Cases

I'm deploying my application to Google App Engine and structure logs for both normal logs as well as error logs is an absolute must to correctly parse any problems.

## Examples

Logging should be tightly integrated with the application. A global logger should be setup and passed into the application as part of the application initialisation (I suggest simply choosing winston by convention). The global logger can then be accessed by the migration scripts, and can also be used inside the `main` function for circumstances where the application doesn't boot.

The HTTP Access Logger should be a middleware that takes a callback with some for such as:
```
LogCallbackFn(logger: WinstonLogger, req: Request, res: Response)
```
This way the logger call can be customised.

## Acceptance criteria

TBD - will be filled by the team.

Start by locating the application initialization path, migration scripts, main function, and HTTP access logging middleware. Clarify the missing acceptance criteria with the team, then define completion as a global structured logger available during boot and migrations plus customizable JSON HTTP access logs suitable for external services.

Written by the indexing model from the issue text.