Updated the documentation about latency and transtype

[ethouris]

1. Added the list of options that are modified by the SRTO_TRANSTYPE option (per a complaint that the order of setting options matters).
2. Modified a bit the information about SRTO_RCVLATENCY option as the features/latency.md document explains it better and in more details.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (8b73dbc) 66.99% compared to head (0f6d2d3) 67.07%.

❗ Current head 0f6d2d3 differs from pull request most recent head 27b72e1. Consider uploading reports for the commit 27b72e1 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2875      +/-   ##
==========================================
+ Coverage   66.99%   67.07%   +0.08%     
==========================================
  Files         103      103              
  Lines       20460    20460              
==========================================
+ Hits        13707    13724      +17     
+ Misses       6753     6736      -17     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[stevomatthews]

Suggested change

	The goal of the latency (TSBPD) mechanism
	=========================================
	The strict goal of this mechanism is to have the time distance between two
	consecutive packets on the receiver side identical as they were at the
	sender side. Obviously this requires some extra delay defined from upside
	that should define when exactly the packet can be retrieved by the receiver
	application, and if the packet arrived earlier than this time, it will have to
	wait in the receiver buffer until this time comes. This time for the packet N
	is roughly defined as:
	```
	PTS[N] = ETS[N] + LATENCY(option)
	```
	where `ETS[N]` is the time when the packet would arrive, if all delays
	from the network and the processing software on both sides are identical
	as they were for the very first received data packet. This means that
	for the very first packet `ETS[0]` is equal to this packet's arrival time.
	For every next packet the delivery time distance should be equal to the same
	packet's declared scheduling time distance.
	The goal of the latency (TSBPD) mechanism
	=========================================
	SRT employs a TimeStamp Based Packet Delivery (TSBPD) mechanism
	with strict goal of keeping the time interval between two consecutive packets
	on the receiver side identical to what they were at the sender side. This
	requires introducing an extra delay that should define when exactly the packet
	can be retrieved by the receiver application -- if the packet arrives early, it must
	wait in the receiver buffer until the delivery time. This time for a packet N
	is roughly defined as:

PTS[N] = ETS[N] + LATENCY(option)

where `ETS[N]` is the time when the packet would arrive, if all delays
from the network and the processing software on both sides are identical
to what they were for the very first received data packet. This means that
for the very first packet `ETS[0]` is equal to this packet's arrival time.
For every following packet the delivery time interval should be equal to the that
packet's declared scheduling time interval.

[stevomatthews]

I made several edits to the text. Please review for technical accuracy.

[maxsharabayko]

To use a consistent style.