feat(meetings): do ip version detection in parallel with reachability

[marcin-bazyl]

COMPLETES #SPARK-562699

This pull request addresses

Orpheus team wants us to tell them if we are on an ipv4 or ipv6 network (or both) when we call the discovery/v1/clusters API. To know this we would need to gather local ICE candidates before making that call - that can take some time (few hundred milliseconds), so for now we will do this in parallel to making the API call just so that we can measure how long it takes and send the timings with reachability metrics.

by making the following changes

• starting ip network detection when we do reachability, but not waiting for it to complete
• sending the information about how long it took in reachability metric

This means that now we'll be sending the ipver parameter to Locus when we're joining a meeting based on the results of ip network detection done during last reachability check. Previously we've just been always sending ipver=0 which means "we don't know if we're on ipv4 or ipv6 network")

Change Type

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Tooling change
• Internal code refactor

The following scenarios where tested

unit tests

I certified that

• I have read and followed contributing guidelines

• I discussed changes with code owners prior to submitting this pull request

• I have not skipped any automated checks

• All existing and new tests passed

• I have updated the documentation accordingly

---

Make sure to have followed the contributing guidelines before submitting.

[aws-amplify-us-east-2]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-3838.d3m3l2kee0btzx.amplifyapp.com

[mkesavan13]

Looks good to me. Do we have a separate Jira for sending the ip version later when we have the duration measured through this metric?

[marcin-bazyl]

Looks good to me. Do we have a separate Jira for sending the ip version later when we have the duration measured through this metric?

Not yet, because depending on the timings we see from the metrics, we'll decide if and how we'll do it. The Jira once created will be added to the parent epic of this PR's jira