Cardano Updates

Bumps [effect](https://github.com/Effect-TS/effect/tree/HEAD/packages/effect) from 3.19.14 to 3.21.0.
- [Release notes](https://github.com/Effect-TS/effect/releases)
- [Changelog](https://github.com/Effect-TS/effect/blob/main/packages/effect/CHANGELOG.md)
- [Commits](https://github.com/Effect-TS/effect/commits/[email protected]/packages/effect)

---
updated-dependencies:
- dependency-name: effect
  dependency-version: 3.21.0
  dependency-type: indirect
...

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

Bumps [flatted](https://github.com/WebReflection/flatted) from 3.3.2 to 3.4.2.
- [Commits](https://github.com/WebReflection/flatted/compare/v3.3.2...v3.4.2)

---
updated-dependencies:
- dependency-name: flatted
  dependency-version: 3.4.2
  dependency-type: indirect
...

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

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

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

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

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

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

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

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

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

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

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

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

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

  Running this on the stdlib was a good test case which bubbled several issues mainly related to generic types; we handle those by simply defaulting to 'Data'.

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

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

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

  There's no point keeping two functions here; it should really just always require the language / plutus version. Also, the 'can_error' boolean is just confusing and as it just reverse the result; which we can simply get by negating it.

  Technically, booleans aren't allowed for Plutus V3, but we use them for tests. So that's now a 'flag' on the function.

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

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

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

The existing `failed()` method applies the same strict success check
(must return Bool(true) or Unit) to all Plutus language versions. This
diverges from the Haskell reference implementation.

Haskell's `processLogsAndErrors` in `PlutusLedgerApi.Common.Eval` only
checks for `EvaluationFailure` for PlutusV1/V2 — any non-error return
value is considered success. The strict Bool(true)/Unit requirement only
applies to PlutusV3.

This adds `failed_with_lang()` which takes a `Language` parameter and
applies version-appropriate success criteria:

- PlutusV1/V2: success = execution completed without error (any return
  value accepted)
- PlutusV3: success = must return Bool(true) or Unit (strict, same as
  existing `failed(false)`)

Real-world impact: PlutusV2 oracle scripts (e.g., Liqwid Finance oracle
on preview testnet) return Data values rather than Bool(true)/Unit, and
are incorrectly rejected by the current implementation.