Updating RetryProxyHandler strategy and retry counts

[fabiocav]

This PR improves the logic in the RetryProxyHandler to accommodate longer worker listener initialization times and address sandbox related issues on Windows consumption.

The new logic uses an exponential strategy, with a cap of 250ms, with a maximum iteration count of 10, allowing for 2100ms of startup time, which based on telemetry data, should be sufficient address the issues we're seeing.

I want to revisit this to make the handler parameters configurable, but this will come in a future iteration.

Pull request checklist

IMPORTANT: Currently, changes must be backported to the in-proc branch to be included in Core Tools and non-Flex deployments.

• Backporting to the in-proc branch is not required
  • Otherwise: Link to backporting PR
• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• My changes do not require diagnostic events changes
  • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
• I have added all required tests (Unit tests, E2E tests)