Additional boundary checks on VideoPlaybackQuality attributes

[tidoust]

Also added checks on the totalFrameDelay attribute, in a separate test because the feature is marked as at-risk in the current CR.

Note the test incorrectly assumed that setting the duration would start a SourceBuffer update, which is no longer true.

[hoppipolla-critic-bot]

Critic review: https://critic.hoppipolla.co.uk/r/6660

This is an external review system which you may optionally use for the code review of your pull request.

In order to help critic track your changes, please do not make in-place history rewrites (e.g. via git rebase -i or git commit --amend) when updating this pull request.

[wpt-pr-bot]

Reviewers for this pull request are: @acolwell, @bit, @shishimaru, @sideshowbarker, and @wolenetz.

[wolenetz]

FF folks landed a conflicting change. I'll work through such conflict after reviewing the rest of these PRs from @tidoust.

FYI-@jyavenard and @tidoust: Chromium change https://codereview.chromium.org/2102323002 also updated (probably with similar conflicts) related tests to accommodate the spec change to disallow duration truncating whole coded frames, and to disallow aborting range removals.

[wolenetz]

VPQ was removed from MSE v1 as it was an at-risk feature. This PR is deprioritized accordingly. I have no objection to including it in the suite, though, since some implementations of it had been done already, and the test improvements will carry over to media playback quality spec, most likely.

[jdsmith3000]

These tests look fine to me, though as @wolenetz notes, they test a section of the spec that has been removed for V1. Merging them in does not seem to be necessary for V1.

[wolenetz]

#3656 replaces this PR. Thank you @tidoust for putting this together.