- Modifies "performSelection" to account for minted and burnt tokens. On a
  superficial level, mints provide extra tokens to use, where burns increase the
  amount of tokens we need to select.
- Modifies the "makeChange" algorithm to account for minted and burnt tokens.
  When tokens are minted they are added to the largest change bundle. When
  tokens are burnt they are removed from the smallest change bundles until the
  burn has been satisfied. See the code for more detailed commentary.
- Adds property tests that ensure the "addMintChange" and "removeBurnChange"
  family of functions:
  - maintain number of change bundles,
  - maintain partial ascending ordering of change bundles
  - modify the total value of the change bundle by their respective mint/burn
    amounts.
- Adds a few unit tests to ensure the change generation occurs as we expect it
  to.
- Adds some debugging information to the coin selection tests to make debugging
  in the presence of minting and burning easier.

- Refactor removeBurnValueFromChangeMaps to make use of the
  "TokenQuantity.difference" and "TokenMap.adjustQuantity" functions, reducing
  the complexity of the implementation (thanks @jonathanknowles).

- Use the new TokenQuantity.difference function to simplify the
  TokenMap.difference implementation (thanks @jonathanknowles).

- Further refactor "removeBurnValueFromChangeMaps" to split out the concepts of
  "subtracting a value from a list of values" and "using that new list to modify
  the quantities of an existing token map". Thanks @jonathanknowles.

Co-authored-by: Jonathan Knowles <[email protected]>

- Thanks to @jonathanknowles for this great suggestion.

This change moves the following responsibilities out of the
`makeChangeForNonUserSpecifiedOutputs` function:

    - the removing of burned values
    - the addition of minted values

This reduces the complexity of property and unit tests that test this
function.

The following functions are still checked by relevant properties:

    - `addMintValuesToChangeMaps`
    - `removeBurnValuesFromChangeMaps`

Further changes will add unit tests to act as documentation and sanity
checks for the above functions.

This commit clarifies documentation and adds explanatory examples for
several functions and fields relating to minting and burning.

…ntError`.

We replace positional arguments with named arguments. (These arguments
are all the same type, so can easily be switched.)

…on`.

In response to review feedback:

https:/input-output-hk/cardano-wallet/pull/2725/files#r655898541

We remove the nested function composition in favour of simple function
composition.

This error should currently never be thrown, as we do not currently
provide a method for the user to mint or burn tokens through the API.

Nevertheless, our test suite requires that we document the error in our
API specification.

This function will be used to verify coverage in coin selection
properties.

…ction_small`.

…riteria`.

In particular, we add coverage for the case where some minted values are
not spent or burned, so we can trigger the `OutputsInsufficient` error.

This assertion should have been negated.

The error was only revealed once we had deliberately tweaked the
generator to generate selection criteria with some minted values
that are not spent or burned.

…ta`.

In the `genAssetsToMintAndBurn` subgenerator for `genMakeChangeData`, we
deliberately create the possibliity of a non-empty intersection between
the sets of assets to mint and assets to burn.