Include ShelleyMA checks

[alegadea]

Related to #7

Using the dev/pallas-applying-public-API pallas branch.

The first step is to classify the checks based on the information they need. Some checks only require transactions, while others require a subset of the UTxO set.

[mikarasv]

The validations from the Shelley MA era are listed below, in a block structure. Blocks start with a statement that describes requirements of the validations within that block. Nested blocks require their requirements and the ones from containing blocks.
Some validations require specific context to validate, those validations (7th to 9th validations) were implemented but not added to the validations list. There are some validations that require context, but were added to the validations list, using hardcoded values (such as ones that need protocol params, era, block slot, and network id).

- The following validation only requires the tx size and the protocol parameters
1. validate_byron_ma_size(size, prot_pps)

- The followiing validations require the transaction
2. validate_shelley_ma_ins_not_empty(mtx_sma)
3. validate_shelley_ma_metadata(mtx_sma)
4. validate_shelley_ma_minting(mtx_sma)

    - The following validation requires the protocol params
    5. validate_shelley_ma_min_lovelace(mtx_sma, prot_pps)

        - The following validation requires the size
        6. validate_shelley_ma_fees(mtx_sma, size, prot_pps)

    - The following validation requires the tx utxos
    7. validate_shelley_ma_ins_in_utxos(mtx_sma, utxos)

        - The following validation requires the era
        8. validate_shelley_ma_preservation_of_value(mtx_sma, utxos, era)
        
        - The following validation requires the transaction witness set
        9. validate_shelley_ma_witnesses(mtx_sma, tx_wits, utxos)
    
    The following validation requires the block slot
    10. validate_shelley_ma_ttl(mtx_sma, block_slot)

    The following validation requires the network id
    11. validate_shelley_ma_network_id(mtx_sma, network_id)