Chrome's decodingInfo rejects the constraint-byte-less 'hvc1.1.L120' and
answers supported:false even on a machine that decodes HEVC fine. The
override then blocked every spelling of tier 1:120, and 1:120 is exactly
what browserDeviceProfile.js's supportsHevc() probes -- so hevc was
dropped from every DirectPlayProfile and the whole HEVC library was
transcoded. Probe the valid 'hvc1.1.0.L120' instead, and only act on
1:120 when no Main tier is usable at all.