deps(sdk): barebones general public client builder.

[Hweinstock]

Problem

start the transition to sdkv3. This PR is just a start, and is intended to serve as an opportunity to look at the design before building on it more. This is still missing a lot of features (see future work).

Excessive line changes are due to package-lock.json changes from install sdk-v3 clients.

Solution

• Do not overwrite existing builder to allow for incremental transition to V3.
• A barebones working model, with the telemetry middleware implemented.
• A proof of concept transition with EC2, unreleased nature makes it low-risk.
• Expansion of testing for client construction.

Future Work

• Implement middleware for other relevant pieces (custom endpoints, logging, etc.).
• Increase testing coverage, specifically with credentials refreshing.
• Migrate other clients.
• Reduce boilderplate for client wrappers.
• replace hand-made mocks with those from sdk mocking library: https://aws.amazon.com/blogs/developer/mocking-modular-aws-sdk-for-javascript-v3-in-unit-tests/

---

License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

[jpinkney-aws]

Out of curiosity what was the idea between calling it Ec2Wrapper? Is it because it's a toolkit wrapper around the sdk v3 builder?

[Hweinstock]

Yeah it seems like a more fitting name, and also because the EC2 v3 exports its client as EC2Client (instead of EC2 as in v2) so want to avoid confusion between the names. Do you think that renaming the 'clients' to 'wrappers' as we migrate them makes sense?