Fixes for buffer and recent regressions

[CastagnaIT]

Description

Fixes found from slack discussion

One of the problems of high memory occupation
is due to
https://github.com/xbmc/inputstream.adaptive/blob/21.1.2-Omega/src/common/AdaptiveStream.cpp#L617-L638
where we set:
assured_buffer_length_ to 60
max_buffer_length_ to 120

in the old code:
https://github.com/xbmc/inputstream.adaptive/blob/Nexus/src/common/AdaptiveStream.cpp#L541-L550
instead set:
assured_buffer_length_ to 4
max_buffer_length_ to 8

this implies we have a very big buffer that require much memory so increase a lot until the end

i think it is better to completely disable this bad code that we have been dragging around for years
now we have almost stable memory occuped, but we can see about 100 mb increased on start (seem regular its debug vs release build)
there is a little memory that increase of about 1mb each time after some seconds that could require other investigations but could be a problem at kodi side (its present also on old isa version)

this bug also reveals another problem on buffering
when we put the playback on pause, we continue download segments where should be paused and resumed when playback will be resumed, this can be improved later, until now this problem was hidden because the buffer is short

Commit: Fallback to ADTS sample reader when TS initialization fails
fix the audio with youtube HLS manifests
where we have wrong container, use file extension is not reliable,
tested with HLS version of https://www.youtube.com/watch?v=Hf5enZVznC4

Motivation and context

fix #1295

How has this been tested?

Screenshots (if appropriate):

Types of change

• Bug fix (non-breaking change which fixes an issue)
• Clean up (non-breaking change which removes non-working, unmaintained functionality)
• Improvement (non-breaking change which improves existing functionality)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that will cause existing functionality to change)
• Cosmetic change (non-breaking change that doesn't touch code)
• None of the above (please explain below)

Checklist:

• I have read the Contributing document
• My code follows the Code Guidelines of this project
• My change requires a change to the Wiki documentation
• I have updated the documentation accordingly

[glennguy]

Thanks for pursuing this until we found an answer!