ISSUE-221 Per request, upgrading dependency goja to v0.0.0-2023081210…

…5242-81d76064690d to include all ES6 features (#222)

This is a major upgrade for omniparser since the upgrade of goja requires go version 1.16, thus we're bumping
omniparser min go version to 1.16 as well. Be careful when you upgrade omniparser.

Wire up the 'csv2' schema handling and write new and update existing …

…docs and samples. (#180)

rename test snapshot filenames that broke module import (#177)

https://cs.opensource.google/go/x/mod/+/master:module/module.go;l=285;drc=02c991387e35f9e4c0a9b7ce137717055f8d716d

so ";" is not allowed in the snapshot filename if the module needs to be imported.

Filed a ticket against cupaloy: bradleyjkemp/cupaloy#83

Adding column index and line matching attributes (line_index, and lin…

…e_pattern) to csv2 column decl and json validation schema (#175)

* Adding column index and line matching attributes (line_index, and line_pattern) to csv2 column decl and json validation schema

Turns out if we want to support multi-line record (whether it's fixed number of rows based or header/footer based) in csv
we will have to let each column to specify which line the column value should come from, and of that particular line, which
indexed value to use, thus the adding of `index`, `line_index` and `line_pattern`.

ISSUE-144: allow schema object property name contains any character (#…

…145)

Perviously we have a validation forcing all output object property name to be only
alpha-numeric (plus underscore). Turns out we have use cases where the property name
might contains special characters such as `'$'` or `'%'`, or `'.'`.

Loosen up the restriction and dealing with all special character in property name
(thus in FQDN) properly with escaping/unescaping.

Update README.md

RawRecord PR follow-up - address DGollings' comment (#139)

Fix issue 137: added `Transform.CurrentRawRecord()` for caller of omn…

…iparser to access the raw ingested record. (#138)

See details in #137.

Deprecate `custom_parse` in favor of `custom_func` (#135)

Deprecated but still functional. Simply removed mention of `custom_parse` from doc and marked it `Deprecated` in public APIs.

Add non-validating edi segment reader, sample and doc (#133)