fix!: resolve hyper error and bubble rejected non-handled exceptions. #12

[TillaTheHun0]

Closes #12
Closes #9

I'm really sorry for the large PR. Most of the diff is utils and tests and lock files. I added a bunch of tests to ensure mappings from ES errors to hyper errors were correct. I can sit down on a call and walk through the changes if that helps.

various bug fixes and error mappings:

• Elasticsearch will automatically create an index, if you attempt to index a document on an index that doesn't exist. It will create an "auto index" and infer fields to index based on document shape. We don't want that, so we check for existing index on indexDoc, updateDoc, bulk before performing the actual operation
• properly map elasticsearch error types to hyper errors ie (index not found, doc not found, invalid mapping, etc.)
• Elasticsearch reserves the _id field on index mappings and documents. So we map _id to a __movedUnderscoreId63__ field internally for mappings, documents, and queries, then back to an _id field when retrieving documents.

I've added a task to the gitpod config to automatically spin up opensearch.

BREAKING CHANGE - caught exceptions are resolved, not rejected, as hyper
errors

The only time a method on the adapter should return a rejected promise
is in the case of an unhandled exception.

Aligns with discussion detailed in:
https://github.com/hyper63/journal/blob/master/design-docs/003-errors.md

[gitpod-io]