Spec errors for VideoFrame sizing exceeding implementation max

Presently Chrome has checks in VideoFrame creation paths like this

  if (coded_width > media::limits::kMaxDimension ||
      coded_height > media::limits::kMaxDimension ||
      coded_width * coded_height > media::limits::kMaxCanvas) {
    exception_state.ThrowTypeError(
        String::Format("Coded size %u x %u exceeds implementation limit.",
                       coded_width, coded_height));
    return nullptr;
  }

This isn't spec'ed. Its not a huge deal, as the limits are large enough that probably no one is hitting them yet, but we should spec it.

Open question whether the exact cutoff should be an impl detail vs some standardized number. @sandersdan @dalecurtis do you recall the origin of the current limits?

Start by reading the linked Chromium implementation in video_frame.cc and the limits in media/base/limits.h, then compare those checks with the WebCodecs VideoFrame creation requirements. Resolve whether the size cutoff should be implementation-defined or standardized, and update the specification to define the intended behavior.