Add HasCallStack constraints to error call sites

[Jimbo4350]

Changelog

- description: |
    Add HasCallStack constraints to functions containing error calls
    for better call stack traces when impossible-state violations occur.
    First step of ADR-011.
  type:
   - compatible
  projects:
   - cardano-api

Context

Implements the first step of ADR-011: Better call stacks of IO exceptions.

This PR adds HasCallStack constraints to ~30 functions across 19 files that contain error calls guarding logically impossible states (e.g. "Impossible! History should always be non-empty", Dijkstra era not-yet-supported guards). When these errors fire, the call stack trace will now be included in the error output, making debugging significantly easier.

This is the simple, low-risk approach: just threading HasCallStack through existing functions. It does not introduce the CIO/runIO/IoeWrapper machinery from the full ADR, which would disrupt the exception catching hierarchy.

Two error call sites were intentionally skipped because they are inside type class instance methods (ToJSON, HasTypeProxy) where the class definition doesn't support HasCallStack.

How to trust this PR

• The change is purely additive — HasCallStack constraints only add call stack propagation, they don't change runtime behavior
• All changes follow the existing pattern established in Cardano.Api.Error (throwErrorM, liftEitherError)
• Library compiles cleanly with cabal build cardano-api:lib:cardano-api

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• New tests are added if needed and existing tests are updated
• Self-reviewed the diff