introduce aws-sdk invocation workaround

[dominikschubert]

Tried to keep it simple here by directly re-using the existing lambda executor for "aws-sdk" integrations (e.g. arn:aws:states:::aws-sdk:sns:createTopic)

A few tradeoffs I've encountered:

• Errors aren't properly mapped right now because they're wrapped in an InvocationException by our lambda API. This should get fixed with the upcoming lambda fixes though.
• Currently only supports aws-sdk invocations without specifying explicit integration pattern. (i.e. task resource ending in .sync or .waitForCallback) will break. The invocation itself is inherently synchronous. Support for these could be added fairly easily though.
• There's now an additional small delay on the first invocation in a region because localstack will lazily create the utility lambda localstack-internal-awssdk upon the first invoke call that contains this function name.

[whummer]

Nice changes @dominikschubert ! 💯 Can we also add the source index.ts and a short script/README on how to generate the compiled index.js?

[whummer]

nit: We could try adding an aspect around getEffectiveInput(..), then we could potentially get rid of the source patches entirely..? (would need to look into the other/existing patches as well, though - just food for thought, maybe in a future iteration..)

[dominikschubert]

Can we also add the source index.ts and a short script/README on how to generate the compiled index.js?

It's basically just a file that is generated by the CDK by bundling with the aws-sdk lib. Maybe it makes more sense to just use the index.js directly and package the aws-sdk in a node_modules folder in a zip file.
Still not super happy about that since the only reason we're not having a single small .js file is a shortcoming in the local executor for node.js (which doesn't provide the aws-sdk lib atm).