Telemetry Crash With Aggressive Report Profile Reload Tests

[shibu-kv]

Problem/Opportunity

Improve telemetry robustness

Steps to reproduce

1. check T2 is enabled in the device; if not, enable it
2. Load the Midlleware build in the device
3. configure the given T2 report profile and leave for soaking
4. check EXLOAD , RELOAD and ON DEMAND (kill -10 , kill -12 & kill -29)

Expected Behavior

Telemetry should not crash

Actual Behavior

Telemetry is crashing

Notes (Optional)

Hard to reproduce. Not seen in production environment.