Use ExecuteHttpRequestWithRetryAsync for (most) every http request

[BMurri]

Problem:
I noticed during a recent transient failure of the unit-integration tests that most of the code is not using the http protocol-specific retry policy exposed through RetryHandler.ExecuteHttpRequestWithRetryAsync. Some code uses less efficient means, most code doesn't try at all.

Solution:
A lot of failures during runtime could be avoided without adding significant time (compared to the costs of retrying entire tasks) by using an efficient retry mechanism, especially one tuned to the metadata returned by the server in the HttpResponseMessage.

Describe alternatives you've considered
Leaving things as they are,

Code dependencies
Will this require code changes in:

• CoA, for new and/or existing deployments? No
• TES standalone, for new and/or existing deployments? No
• Terra, for new and/or existing deployments? No
• Build pipeline? No
• Integration tests? No

Additional context
TBD