Version 3.9 of proposal to change the TrafficShapingHandlers

Motivation:
Several issues were shown by various ticket (#2900 #2956).

Issue #2900
When a huge amount of data are written, the current behavior of the
TrafficShaping handler is to limit the delay to 15s, whatever the delay
the previous write has. This is wrong, and when a huge amount of writes
are done in a short time, the traffic is not correctly shapened.

Moreover, there is a high risk of OOM if one is not using in his/her own
handler for instance ChannelFuture.addListener() to handle the write
bufferisation in the TrafficShapingHandler.

Without "user manage writability" capability added to the channel,
writability could be managed, using isWritable() and one of the methods
proposed by TrafficShapingHandler among:
- checkWriteSuspendedOne(ctx): if only one TrafficShapingHandler is in the pipeline
- checkWriteSuspendedMultiple(ctx): if multiple TrafficShapingHandler are in the pipeline
- checkWriteSuspendedOne(ctx, handler): to check against one specific TrafficShapingHandler

ChannelInterestChanged is also managed in order to provide some compatibility
with other handlers as for instance HttpChunkedInput.

The "bandwidth" compute on write is only on "acquired" write orders, not
on "real" write orders, which is wrong from statistic point of view.

Issue #2956
When using GlobalTrafficShaping, every write (and read) are
synchronized, thus leading to a drop of performance.
ChannelTrafficShaping is not touched by this issue since synchronzed is
then correct (handler is per channel, so the synchronized).

Modifications:
The current write delay computation takes into account the previous
write delay and time to check is the 15s delay (maxTime) is really
exceeded or not (using last scheduled write time). The algorithm is
simplified and in the same time more accurate.

This proposal handles the channelInterestChanged(), filtering the
events. This allows in some extent the compatibility with code using
natively channelInterestChanged(). However, wihtout "user manage writability" as
proposed in 4.X, one should add a special management through various helper methods, as exposed in the Discard example.

When the real write occurs, the statistics are update accordingly on a
new attribute (getRealWriteThroughput()).

To limit the synchronisations, all synchronized on
GlobalTrafficShapingHandler on submitWrite were removed. They are
replaced with a lock per channel (since synchronization is still needed
to prevent unordered write per channel), as in the sendAllValid method
for the very same reason.
Also all synchronized on TrafficCounter on read/writeTimeToWait() are
removed as they are unnecessary since already locked before by the
caller.
Still the creation and remove operations on lock per channel (PerChannel
object) are synchronized to prevent concurrency issue on this critical
part, but then limited.

Result:
The traffic shaping is more stable, even with a huge number of writes in
short time by taking into consideration last scheduled write time.

The traffic shaping is more compatible with code as ChunkedWriteHandler,
but up to a certain extent, in the sens that it does not prevent fully
OOM since isWritable is only managed by the channel properties, not by
adding a "user manage writability". However, globally, it seems limiting
natively even for ChunkedWriteHandler correctly the memory usage.

The statistics are more valuable (asked write vs real write).

An example is shown in the Discard example (example/discard), and
in particular how a user handler might managed the write to prevent OOM:

- using the ctx.getChannel().isWritable() in conjunction of one of the proposed methods
(checkWriteSuspendedOne(ctx), checkWriteSuspendedMultiple(ctx), checkWriteSuspendedOne(ctx, handler))
- using channelInterestChanged() to continue writing

The Global TrafficShapingHandler should now have less "global"
synchronization, hoping to the minimum, but still per Channel as needed.