feat: update vaa-shared and vaa-matching

[kaljarv]

WHY:

• Makes changes needed for vaa module interoperability.
• Updates vaa-matching so that more question types and algorithmic variants can be implemented with it. The shortcomings of the current model were discovered during implementing the vaa-data model (feat: vaa-data module #595)

What has been changed

Move those types and some utilities to vaa-shared that need to match
between all of the modules. These include:

• The Id type used for objects with unique ids
• Types related to data passed to the matching algorithm in
  vaa-matching, such as distances, coordinates, missing values and
  requirements for questions used for matching
• Some utilities related to these types

Update vaa-matching on a variety of counts:

• Remove the types that are defined in vaa-shared
  324fdd8
• Rewrite handling of subdimensions so that they can be used universally
  with all distance metrics. This involves restructuring the metric
  functions in a composable format
• Implement a Euclidian distance metric
• Remove the AbsoluteMaximum missing value imputation method because
  it does not fit the general mathematical matching model
• Create an example implementation of CategoricalQuestion for multiple
  choice questions whose values cannot be ordered
• Change both question implementation to adhere more closely to the
  upcoming vaa-data model
• Implement passing of question weights to the matching algorithm
• Abbreviate and rename some types
• Apply the new TS style guide requirements to the code
• Rewrite many of the tests
• Update the README

Apply the required changes to consumers of these modules.

Check off each of the following tasks as they are completed

• I have reviewed the changes myself in this PR. Please check the self-review document
• I have added or edited unit tests.
• I have run the unit tests successfully.
• I have run the e2e tests successfully.
• I have tested this change on my own device.
• I have tested this change on other devices (Using Browserstack is recommended).
• I have tested my changes using the WAVE extension
• I have added documentation where necessary.
• Is there an existing issue linked to this PR?

Clean up your git commit history before submitting the pull request!

[gogarufi]

It looks solid to me. Seems that the shared tests work as they should - without having to be transpired into .js sources. Nice! :)

[kaljarv]

Merging this even though the e2e test fails because it will be corrected in the next PR to be merged, and the failure is not due to the changes in this PR.