fix: Fix Memory Leaks & other minor fixes

[binaryoverload]

Resolves the memory leak! Leaving this in draft for ~24 hours while I test on prod to ensure it's fixed

Credit to @TortleWortle for initially figuring out the quirk with .pipe

Changes:

• Added @smithy/types to correctly type the S3 client so we don't have to weirdly cast things
• Use Stream.pipeline to fix the memory leak with S3 requests staying in memory if the NPDL request isn't closed nicely
• Removed all sync IO in HTTP requests and replaced with call backs to reduce blocking
• Update dependencies and fix some automatically fixable linting issues
• Update logger to properly pad time and have date (For tracking down errors)
• Fix typo in Content-Type header

• I have read and agreed to the Code of Conduct.
• I have read and complied with the contributing guidelines.
• What I'm implementing was an approved issue.
• I have tested all of my changes.

[DaniElectra]

Actually nevermind, looks like the applicatoin typo is actually intended and is what the official server sets. Can you revert back that and add a comment about it being intended?

[jonbarrow]

Overall the actual functionality changes look great 👍 many thanks for finding this! Review is almost entirely nits for styling reasons (as discussed on Discord this is not your fault, we don't have this posted anywhere) and a couple questions

(some things apply to the whole PR, though I've only commented once)

[jonbarrow]

Gorgeous, only one question and that's it

[jonbarrow]

LGTM! Great work!