It is very hard to debug `ValidationNotEqualError` without offsets
In JS current implementation of `ValidationNotEqualError` (and other errors) does not contain an offset, which makes debug of KSY a nightmare. However, JS generator in Web-IDE shows, that constructor gets much more parameters, that it handles:
```js
Cassette.prototype._read = function() {
  this._debug._unnamed0 = { start: this._io.pos, ioOffset: this._io.byteOffset };
  this._unnamed0 = this._io.readBytes(1);
  this._debug._unnamed0.end = this._io.pos;
  if (!((KaitaiStream.byteArrayCompare(this._unnamed0, [30]) == 0))) {
    throw new KaitaiStream.ValidationNotEqualError([30], this._unnamed0, this._io, "/types/status/types/supply_counts/types/ci01/types/cassette/seq/0");
  }
  ...
}
```

https://github.com/kaitai-io/kaitai_struct_javascript_runtime/blob/03c8bf24e357cff62b6269d106f87650c3c0c578/KaitaiStream.js#L791-L797

The error message in Web-IDE is very unhelpful:
> Parse error (ValidationNotEqualError): not equal, expected [30], but got [48]
> <...stack...>

1. first, there no offset where the error is occurred
2. second, it shows decimal values, whereas HEX editor shows HEX values, so it is hard to match one with other
3. third, it is unclear in which field error is happened