Crt and package lock update

• Update to latest CRT and manually pin several packages

Updating CRT to 1.6.2

BUG FIX

• The authentication of proxy option will propagate correctly now
• Building issues related to aws-lc is solved on some ARM machine.

API updates from aws-crt

• Deprecated with_timeout_ms method as it's out of date. The with_timeout_ms will be moved to with_ping_timeout_ms to configures the PINGREQ response timeout
• Add new with_protocol_operation_timeout_ms to configure the protocol operation timeout.

Updating CRT to 1.5.5

• Updating CRT to 1.5.5:
  • Integration with aws-lc for crypto
  • CRT Related BUG FIXES:
    • Memory was being incorrectly released in MQTT connection finalize.
    • Pub-sub samples from iot-device-sdk-js-v2 were exiting with a non-zero code.
    • MQTT on_publish callback was not being cleaned up.
    • Async callbacks invoked with invalid env, leading to a crash.
    • The event-loop-group created for node was not getting cleaned up.
    • Async write operation for a Buffer Array based on a C managed buffer would crash, as the C buffer get cleaned up after the callback, before the async operation finishes.
• Other BUG FIXES:
  • Adding disconnects to samples to prevent connection related hang.

aws-crt 1.5.2

aws-crt 1.5.2 (#137)

fixes aws-c-cal submodule

MQTT on-message callbacks carry more info + Bugfixes

• IMPROVEMENT: The MQTT on_message event, and the topic-specific callback passed to subscribe(), have added dup, qos, and retain params.
• IMPROVEMENT: Outgoing MQTT Payload type now accepts ArrayBuffer and any ArrayBufferView (ex: Uint8Array) type.
• BUGFIX: on_message payload typescript signature changed from Buffer to ArrayBuffer.
  • This is a semi-breaking change. There were two callback passing payloads, one signature claimed to pass ArrayBuffer payloads and the other claimed to pass Buffer payloads. In reality the node implementation always passed ArrayBuffer and the browser implementation always passed Buffer. Now, both callbacks share a signature, they both claim to pass ArrayBuffer and both the node and browser implementations actually do pass ArrayBuffer
• BUGFIX: browser MQTT publish() no longer tries to turn everything to strings. ArrayBuffer and ArrayBufferView types will pass their bytes straight through.
• BUGFIX: browser MQTT unsubscribe()

Fix crash on MQTT websocket reconnect

v1.3.6

aws-crt 1.3.7 (#125)

Update dependencies

update [email protected] (#123)

also run `npm update` on all package.json files

Try-Lock fix on Windows

• fixes a fatal assert on Windows when aws_mutex_try_lock was called

Stability fixes

• Fixes crash invoking Openssl APIs when there's a mismatch between node's openssl and the openssl the sdk was built against
• Fixes crash on shutdown due to not waiting for thread-based C objects to completely destroy themselves.

Update s2n to release v0.10.19

• Update s2n to release v0.10.19