Messaging session bug fix

[manasisurve]

Issue #:
#2372

Description of changes:

1. Fix to break infinite reconnect loop in messagingSession on timeout. Reported here Chime chat(messaging) messagingSessionDidStop did not fire on disconnect #2372
2. Add backwards compatibility with aws-js-sdk 2.x for getMessagingSessionEndpoint call

Testing:

• Tested reconnect loop fix by expiring credentials to validate reconnect loop on messagingSession breaks after the timeout

• Tested compatibility with aws sdk v2 by changing the chime client instantiation in the messagingSession demo

• Set aws credentials with in correct aws session token

• Run the messagingSession demo here: https://github.com/aws/amazon-chime-sdk-js/tree/main/demos/browser. npm run start --app=messagingSession

• connect with an app instance user

• Reconnect loop is triggered but breaks after timeout

Can these tested using a demo application? Please provide reproducible step-by-step instructions.
To Test aws js sdk v2 compatibility run the messagingSession demo with below changes
Make the following changes in amazon-chime-sdk-js/demos/browser/app/messagingSession/messagingSession.ts

import { ChimeSDKMessagingClient } from '@aws-sdk/client-chime-sdk-messaging'
to
import * as Chime from 'aws-sdk/clients/chime';

and change

 const chime = new ChimeSDKMessagingClient({ region: 'us-east-1', credentials: response });
to
const chime = new Chime({ region: 'us-east-1', credentials: response });

To Test aws js sdk v3 with v2 style run the messagingSession demo with below changes
Make the following changes in amazon-chime-sdk-js/demos/browser/app/messagingSession/messagingSession.ts

import { ChimeSDKMessagingClient } from '@aws-sdk/client-chime-sdk-messaging'
to
import { ChimeSDKMessaging } from '@aws-sdk/client-chime-sdk-messaging';

and

 const chime = new ChimeSDKMessagingClient({ region: 'us-east-1', credentials: response });
to
const chime = new ChimeSDKMessaging({ region: 'us-east-1', credentials: response });

and then run
Checklist:

1. Have you successfully run npm run build:release locally?
   yes

2. Do you add, modify, or delete public API definitions? If yes, has that been reviewed and approved?
   no

3. Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved?
   no
   By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
   yes

[devalevenkatesh]

nit: Back tick firstConnectionAttemptTimestamp and startedConnectionAttempt.

[devalevenkatesh]

Is the package-lock.json changes necessary?

Does not look like from the fix that those are needed.

The base branch was changed.

[devalevenkatesh]

Closing due to #2444