Cardano Updates

Signed-off-by: KtorZ <[email protected]>

Correctly handle credentials in certificates in v1 & v2

  We now provide the following behaviour:

  - By default, expect statements still generate a trace from the source code in verbose-mode.
  - When preceded with a doc comment `///`, expect will use the comment as a trace instead of generating it.
  	- When in `compact` mode, we attempt to hook onto any label (text before `:`) to be consistent with normal traces.
	- When in `verbose` mode, we use the entire comment as trace.

Signed-off-by: KtorZ <[email protected]>

Signed-off-by: KtorZ <[email protected]>

  The goal is to let 'expect' kind of assignment carry an optional comment which can be used as trace instead of the auto-generated UPLC trace. While the plan is to re-use the doc-comment syntax for this, it won't be parsed as comment; but will instead be parsed as an annotation for 'expect'

Signed-off-by: KtorZ <[email protected]>

Signed-off-by: yHSJ <[email protected]>

  Closes #1207.

Signed-off-by: KtorZ <[email protected]>

Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.1.0 to 4.1.1.
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](https://github.com/nodeca/js-yaml/compare/4.1.0...4.1.1)

---
updated-dependencies:
- dependency-name: js-yaml
  dependency-version: 4.1.1
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>

Bumps [glob](https://github.com/isaacs/node-glob) from 10.4.5 to 10.5.0.
- [Changelog](https://github.com/isaacs/node-glob/blob/main/changelog.md)
- [Commits](https://github.com/isaacs/node-glob/compare/v10.4.5...v10.5.0)

---
updated-dependencies:
- dependency-name: glob
  dependency-version: 10.5.0
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>

  Closes #1087.

Signed-off-by: KtorZ <[email protected]>

  Fixes #1206.

Signed-off-by: KtorZ <[email protected]>

Fixes #1211

Signed-off-by: KtorZ <[email protected]>

  Fixes #1187.

Signed-off-by: KtorZ <[email protected]>

  Fixes #1198.

Signed-off-by: KtorZ <[email protected]>

  Fixes #1170.

Signed-off-by: KtorZ <[email protected]>

  - Return a generic error message when no help is available on the
    error (still showing the location of the problem)

  - Use related errors to find labels on where to report errors for
    those with no immediate location (e.g. UnknownLabels).

  Fixes #954.

Signed-off-by: KtorZ <[email protected]>

  Fixes 1137.

Signed-off-by: KtorZ <[email protected]>

  We cannot actually keep a cache of generics around during reification
  because the type comes from the stored data_types definitions, and
  thus only refer to a single generic_id.

  So, when reifying a value that carry, for example, two Options. Each
  should have a different generic id for their inner type parameter.
  Yet, because we pull the type from the stored data_types definitions
  (and not from the context of the whole program); their generic ids
  during reification will be the exact same.

  Said differently, generic ids are useless during reification; other
  than for indicating that there's a generic. Fortunately, since the
  instantiated type definition is available during reification, we can
  simply replace the generic in-place with its instantiated value when
  reifying.

  Fixes #1172.
  Fixes #1179.

Signed-off-by: KtorZ <[email protected]>

  Fixes #1144.

Signed-off-by: KtorZ <[email protected]>

  This is actually safe, as demonstrated by the property introduced in
  this commit; the intuition for it is that we re-order arguments by
  swapping their positions. So if only one positional argument comes
  after all the labeled one, it will necessarily end up in the correct
  positions after all the labeled ones have been placed in their
  position.

  Fixes #1164.

Signed-off-by: KtorZ <[email protected]>

  Fixes #1144.

Signed-off-by: KtorZ <[email protected]>

Signed-off-by: KtorZ <[email protected]>

  This is actually safe, as demonstrated by the property introduced in
  this commit; the intuition for it is that we re-order arguments by
  swapping their positions. So if only one positional argument comes
  after all the labeled one, it will necessarily end up in the correct
  positions after all the labeled ones have been placed in their
  position.

  Fixes #1164.

Signed-off-by: KtorZ <[email protected]>

  Fixes #1144.

Signed-off-by: KtorZ <[email protected]>