Reduce usage of patterns

[smelc]

Changelog

- description: |
    Reduce usage of patterns
# 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
  # - refactoring    # QoL changes
  # - 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

Our codebase is hard to enter. It's big, it redefines types with the same names from the ledger, it has a complex witness system, it has historical quirks. This PR aims at reducing one of the things you need to understand to contribute to this codebase: patterns. The patterns that are removed by this PR are easily replaced by a few functions calls there and there. This shows on the count of lines changed: it's more deletion (51) than additions (22).

In additions, this barely impacts the CLI, as the corresponding CLI PR shows.

For the record, this PR is a spin-off of this work: #724

Follow-up

If this one obtains support, I can go further and delete more patterns. Up to reviewers to tell me which direction to go.

How to trust this PR

Highlight important bits of the PR that will make the review faster. If there are commands the reviewer can run to observe the new behavior, describe them.

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• Self-reviewed the diff

[carbolymer]

I don't know about this change - I don't know how popular are patterns across cardano-api consumers. Those patterns are convenient, but somewhat magical, like TxBody, doing suddenly a whole conversion.

@Jimbo4350 thoughts?

[carbolymer]

👍🏻