feat(logging): CW client, deviceId & NetworkMonitor

[Samaritan1011001]

Description of changes

This PR brings in the following three main pieces:

1. [logging] CloudWatch client -- contains the log, flushLogs and configure methods
   a. Example format of the log message sent to CloudWatch -- [${logLevel}] ${namespace}/${category}: ${message}
2. [core] deviceId impl
3. [core] NetworkMonitoring impl -- module to run a handler when the device comes back online.

There are a couple of TODOs in the CW client that is left for further addition to the implementation.

Issue #, if available

Description of how you validated changes

1. React app using the CW provider to log
2. Checked local store to see saved logs
3. Unit tests confirm behavior of proposed changes

Checklist

• PR description included
• yarn test passes
• Tests are changed or added
• Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[ashwinkumar6]

Great work @Samaritan1011001 !!
Just a couple of questions and nits for refactoring based on the previous PR merged

[ashika112]

I am good overall with this. I think we need to re-arrange and organize some utils function but good to followup with another PR.

[ashwinkumar6]

Thanks @Samaritan1011001, Looking good
Just a couple of nits and questions

I'm good with also adding TODOs and getting this merged

[ashwinkumar6]

nit
I'm wondering if we should break up this entire object into separate functions.

For internal logs the API that exposes the CW object could just be something like

export const cloudWatchProvider: LoggingProvider = {
    log: (logParams: LogParams) => {
        logToCloudWatch(logParams);
    }
};

Also with the recent design proposal, we're planning to just expose CW provider enable/disable instead of the entire category level enable/disable so I think we should be fine