feat: enhanced support for dmt with source config changes as well as retrying with backoff

[desusai7]

Enhanced support for DMT

1. Source Config Flag change from areTransformationsConnected to shouldApplyDeviceModeTransformation to understand if a device mode destination had transformations connected to it.
2. Parsing a New Flag propagateEventsUntransformedOnError from, which says should original events be sent back to a destination on transformation failure
3. Retrying with exponential backoff for the requests made to the transformation service with a delay starting at 500ms and a max limit of 1000ms with almost 2 retries
4. When network requests to DMT service fails even after backing off and retries getting exhausted, then we would dump back the original events to the destination factories based on the new flag in propagateEventsUntransformedOnError.

5. When we received success response from the DMT service then we will check the status at each event level.
   -> If 200 we will dump the transformed event to factories,
   -> If the status is 410|4xx we will dump the original events based on the new flag propagateEventsUntransformedOnError and detailed logs accordingly

6. Include destination Ids at each event level based on the user consent, event filtering, and integrations object in the request being sent to the DMT service
7. If we are dumping original events, utilize the destination Ids from the request object and dump to them
8. Disable Gzip for requests made to the DMT service
9. Handle network un-availability by breaking out of do-while immediately and stop the data loss because even retries would fail

[desusai7]

same as #342, but opened it again because of github not adding the merge commit to the PR and still showing the conflicts

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

3.3% Coverage
0.0% Duplication