feat: added typing for patterns

[lkhari]

What did you implement:

I've created some typing for correlation-middleware, to add some clarity on where the correlationId and logger has been added, since the sqs capture correlationId puts the logger on the event and the capture streams exposes them on the context.

I've also exposed the Logger in correlation-middleware and appended it to the patterns. This just to reduce having to import both Logger and correlation-middleware. Due to the assumption that if I got the correlation-middleware I most likely will be using the logger.

How did you implement it:

Added a index.d.ts file and on the index.js exposed the logger as a named export.

How can we verify it:

Create a typescript project import logger and see ;)

Todos:

• Write tests
• Write documentation
• Fix linting errors
• Make sure code coverage hasn't dropped
• Provide verification config / projects / resources
• Enable "Allow edits from maintainers" for this PR
• Update the messages below

Is this ready for review?: Yes
Is it a breaking change?: NO

[lkhari]

Any opinions on the work done @gsingh1 ? I haven't exposed all of lambda Types, thinking it shouldn't be our responsibility to deal with all of them. So I've only exposed the types in which we've affected.

[gsingh1]

Hey @lkhari, thanks for this. LGTM and I think we can start adding the others as and when required.

[simontabor]

Thanks @lkhari and sorry for the slow reviews. Types look fine (haven't tested directly myself though)

Exposing Log should be moved to an issue/feature proposal so this PR doesn't get held up further

[simontabor]

LGTM, thanks for the changes! Just one small comment for default Log value

[lkhari]

@simontabor or @gsingh1 can this be merged? The ability for custom logger shouldn't affect this story, since this this is just types for the current library.