Previously, if an extended opcode was truncated, it would manifest as an "unexpected line op length error" which wasn't quite accurate. This change checks for errors any time data is read whilst parsing an extended opcode, and reports any errors detected.
Depends on D80796.
Does it help clarity using DataExtractor::Cursor and StringRef getCStrRef(Cursor &C) const?