upgrade (transfer tx) handles 1100 problem

[victormimo]

What?

• Refactors transfer functionality. Now the user interacts with a HOF that determines how many transfers are needed to satisfy the amount inputted, ensuring that the user has enough shares across their activePositions.
• Created an ethers test script in the server to quickly test all API end points programmatically.
• Creates a nonce for deterministic UUIDs
• Refactors server to deploy and read specific cap tables (and creates listeners for those), saving the deployed to. address in the issuer.

Linear tickets:

• https://linear.app/poetnetworkhq/issue/TAP-236/save-cap-table-address-to-fetch-the-right-issuer
• https://linear.app/poetnetworkhq/issue/TAP-176/improve-deterministic-uuids-for-transactions
• https://linear.app/poetnetworkhq/issue/TAP-158/finish-stock-tx-extend-to-handle-multiple-positions-to-sell-1100
• https://linear.app/poetnetworkhq/issue/TAP-260/create-a-new-model-to-capture-transaction-history-for-easy-querying

Question

• Do we need to copy over the data from the original issuance tx of the transferor in the issuance tx of the transferee? it wouldn't make sense to, but it's worth asking. Right now, we're not doing that, rather filling out a "minimal" issuance with only required fields.