fix(FEC-11734): player error handling works incorrect

[yairans]

Description of the Changes

This is a shaka issue - shaka-project/shaka-player#3794
As a WA - set the error severity to critical when it's HTTP_ERROR

Solves FEC-11734

CheckLists

• changes have been done against master branch, and PR does not conflict
• new unit / functional tests have been added (whenever applicable)
• test are passing in local environment
• Travis tests are passing (or test results are not worse than on master branch :))
• Docs have been updated

[OrenMe]

@yairans the proper way to handle this for Shaka, which is basically what you did in our code is to use failureCallback method in streaming config.
It is connected to the deprecated option shaka once had called infiniteRetriesForLiveStreams which from the name you can understand what is the default behaviour for shaka for live manifests reloads and why it internally sets this error to non fatal.

this is the default handler for them and you can see it sets for live a few errors to be non fatal https://github.com/google/shaka-player/blob/master/lib/player.js#L4960

[yairans]

@OrenMe The question is why this behavior is only in SegmentTimeline and not in SegmentTemplate?
see the shaka issue I opened for more details.
anyway, I tested the failureCallback config and it doesn't work, seems because the error is not caught as I wrote in the shaka ticket.

[OrenMe]

so this will happen also for VOD if we use SegmentTimeline? although in VOD manifest won't ever reload so not a real issue.

I just suspect doing this in error handler for all playback types might be an issue cause this will cause any HTTP error to get us into critical error, meaning error handling will be void