feat(ec2-metadata-service): add retries for IMDS requests

[siddsriv]

Issue

Internal JS-5193

Description

Support retries for EC2 IMDS requests and fetching tokens.

Testing

Unit tests:

 ✓ src/MetadataService.spec.ts (24 tests) 20ms
   ✓ MetadataService Socket Leak Checks > fetchMetadataToken - body consumption checks > should consume response body on 200 status and return token 5ms
   ✓ MetadataService Socket Leak Checks > fetchMetadataToken - body consumption checks > should consume response body on 400 status before throwing 2ms
.
.
.

   ✓ MetadataService Retry Configuration > status code handling for retries > should not retry 403 errors 0ms
   ✓ MetadataService Retry Configuration > status code handling for retries > should not retry 404 errors 0ms
   ✓ MetadataService Retry Configuration > status code handling for retries > should retry 401 errors 0ms
   ✓ MetadataService Retry Configuration > status code handling for retries > should retry 500 errors 0ms

 Test Files  1 passed (1)
      Tests  24 passed (24)
   Start at  23:37:49
   Duration  354ms (transform 72ms, setup 0ms, collect 96ms, tests 20ms, environment 0ms, prepare 78ms)

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[kuhe]

docs should say:

If the function returns a promise, it will be awaited and its resolved value ignored.
If the function returns a number, the number will be used as a millisecond duration to wait before the following retry attempt.

[kuhe]

use milliseconds for time, since that is the time unit idiomatic to the language? how is the specification on this?