Do not allow submitting transactions older than current node era

[newhoggy]

Changelog

- description: |
    Do not allow submitting transactions older than current node era
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  - breaking       # the API has changed in a breaking way
  # - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - improvement    # QoL changes e.g. refactoring
  # - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
  # - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...

Context

Submitting transactions older that the current node era is unsafe.

This PR also removes all uses of EraCast from cardano-api.

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• The change log section in the PR description has been filled in
• New tests are added if needed and existing tests are updated. These may include:
  • golden tests
  • property tests
  • round trip tests
  • integration tests
    See Running tests for more details
• The version bounds in .cabal files are updated
• CI passes. See note on CI. The following CI checks are required:
  • Code is linted with hlint. See .github/workflows/check-hlint.yml to get the hlint version
  • Code is formatted with stylish-haskell. See .github/workflows/stylish-haskell.yml to get the stylish-haskell version
  • Code builds on Linux, MacOS and Windows for ghc-8.10.7 and ghc-9.2.7
• The changelog section in the PR is updated to describe the change
• Self-reviewed the diff

[carlhammann]

What's the purpose of this value?

[Jimbo4350]

I think we don't need the originalValue field. It's probably enough to say the node is in an unexpected era and what era that is.

[newhoggy]

The field is so that if we have some value that is in the wrong era for example TxOut era then we can print out a useful error message to say what it was that was in the wrong era. @Jimbo4350 is right that we don't need it because we now outright reject circumstances where eras don't match rather than before when we were more lenient and additional context was helpful.

The field has been removed.

[Jimbo4350]

One minor comment. Happy to approve after.

[Jimbo4350]

I think we don't need the originalValue field. It's probably enough to say the node is in an unexpected era and what era that is.