fix(WPB-15487): fix coturn port range in all the documentation

[mohitrajain]

Change type

• Fix
• Feature
• Documentation
• Security / Upgrade

Basic information

• THIS CHANGE REQUIRES A DEPLOYMENT PACKAGE RELEASE
• THIS CHANGE REQUIRES A WIRE-DOCS RELEASE

Testing

• I ran/applied the changes myself, in a test environment.
• The CI job attached to this repo will test it for me.

Tracking

• I mentioned this PR in Jira, OR I mentioned the Jira ticket in this PR.
• I mentioned this PR in one of the issues attached to one of our repositories.

Knowledge Transfer

• An Asciinema session is attached to the Jira ticket.

Motivation

Objective

Reason

The port range is still pointing to restund port range and we should consider the coturn operating ports.

https://github.com/wireapp/coturn/blob/wireapp/4.6.2-helm-chart/src/apps/relay/turn_ports.h#L44

#define LOW_DEFAULT_PORTS_BOUNDARY (49152)
#define HIGH_DEFAULT_PORTS_BOUNDARY (65535)

https://www.rfc-editor.org/rfc/rfc5766 Page 26

   In all cases, the server SHOULD only allocate ports from the range
   49152 - 65535 (the Dynamic and/or Private Port range [Port-Numbers]),
   unless the TURN server application knows, through some means not
   specified here, that other applications running on the same host as
   the TURN server application will not be impacted by allocating ports
   outside this range.

We should also highlight the outbound incase of strict outbound rules.
https://docs.wire.com/understand/notes/port-ranges.html

Use case

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud