Add Cardano.Api.Tx.Compatible

[Jimbo4350]

Changelog

- description: |
    This module exposes `createCompatibleSignedTx` which is intended to be used in testing only. It allows the creation of simple unbalanced transactions that can submit protocol updates in any era.
# uncomment types applicable to the change:
  type:
  - feature        # introduces a new feature

Context

Additional context for the PR goes here. If the PR fixes a particular issue please provide a link to the issue.

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
• New tests are added if needed and existing tests are updated. See Running tests for more details
• Self-reviewed the diff

[palas]

Looks good 👍
Just a couple of lints

[palas]

Suggested change

	txbody =
	conwayEraOnwardsConstraints conwayOnwards $
	createCommonTxBody sbe ins outs txFee'
	& L.proposalProceduresTxBodyL
	.~ OSet.singleton updateProposalProcedure
	bodyWithProtocolUpdate =
	conwayEraOnwardsConstraints conwayOnwards $
	createCommonTxBody sbe ins outs txFee'
	& L.proposalProceduresTxBodyL
	.~ OSet.singleton updateProposalProcedure

Best to use the same terminology as other branches. I would also recommend moving common bits to outside the case, but I've tried, and it seems the Haskell constraint solver doesn't like that at all

[Jimbo4350]

This is still a WIP as it's being integrated in cardano-cli and needs to be tested by QA.

[carbolymer]

The module name and the description is not quite clear for me. Is it supposed to be a module for support of transaction building for older eras once we remove them from API?

Maybe we should add Internal to the module name e.g. Cardano.Api.Tx.Internal.Compatible, to mark that it's not meant to be directly used?

I'm not sure about the name as well. Maybe we should name it something like Old or Legacy to put emphasis that it's meant just for backwards compatibility for tests.

[Jimbo4350]

It's meant to be directly used. It's supposed to house all functions that are expected to be backwards compatible across all shelley based eras. I'm not opposed to a rename but I'm not blocking the PR on this.