Support for addresses with staking keys and wallet lookups.

[zmrocze]

This is the current "Staking keys support" pr for plutip. related Issues: #103 #104

• Add stake keys to BpiWallet.
• Generate stake keys in addWallets
• Set pcOwnStakePubKeyHash for BPI.
• Pass WalletLookups to contracts instead of list of PubKeyHash's.
• wallets initialized with WalletTag which specifies a) how wallet is generated b) how wallet is accessed in test case

Contains changes introducing staking keys support, but together with changes to the wallet initialization and to the interface of providing user with keys in the contract.

It aims to provide lookups like so:

assertExecution
  "Values asserted in correct order with withContract"
  (initAda (EnterpriseTag "w0") [100]
    <> initAda (BaseTag "w1") [200]
  )
  (withContract $ \wl -> do
    EnterpriseInfo w1pkh <- lookupWallet wl (EnterpriseTag "w0")
    BaseInfo w2pkh <- lookupWallet wl (BaseTag "w1")
    _ <- payTo w1pkh (toInteger payTo1Amt)
    _ <- waitNSlots 2
    payTo w2pkh (toInteger payTo2Amt))
  [shouldSucceed]

EDIT: nevermind

[zmrocze]

For this wallet WalletInfo is calculated twice from BpiWallet (second time in withContractAs). makeWalletInfo basically calculates pubkey hashes. runContract can be fed WalletInfo instead of BpiWallet, calculating one hash less, no problem. I only put it like that, to change less in interactive-plutip docs. Unsure..

[zmrocze]

I removed substituteTags from withConfiguredCluster. Before it basically acted as identity, only adding the type info and making things compile, now can get rid of.
edit: A and removed comment "This test doesn't fail because negative amount". I dont get this comment now, I think i've been seeing ghosts haha

[zmrocze]

will note here, as probably won't be able to work on this, that this change enables #121 with no more api changes. Simmilarly extra-signing-keys could be initialized in TestWallets (tho no need to remove them from config as second option).