feat: add sending l2 tx

[Tuditi]

Summary

This PR adds support for L1 -> L2 transactions.

Changelog

- Add getLayer2TransactionData function
- Removed metadata and tag when creating newTransactionDetails
- Added draft TextInput

Relevant Issues

closes: #4981

Testing

Alias Output address representing SMR network: rms1pzw5y4e4y6gzkytvjp0ukgjgs37vd33uvnju9tuf6rrztnnw4tj7crw72ar

Follow the guide here to set-up your metamask for the Shimmer EVM: https://hackmd.io/SWpeUi_eTDKbnvK623vMmw#Configuring-MetaMask

In Firefly select the Shimmer EVM from the network drop-down and then input your EVM address in the recipient field (needs polish).

Platforms

Please select any platforms where your changes have been tested.

• Desktop
  • MacOS
  • Linux
  • Windows
• Mobile
  • iOS
  • Android

Instructions

Please describe the specific instructions, configurations, and/or test cases necessary to test and verify that your changes work as intended.

...

Checklist

Please tick all of the following boxes that are relevant to your changes.

• I have followed the contribution guidelines for this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or modified tests that prove my changes work as intended
• I have verified that new and existing unit tests pass locally with my changes
• I have verified that my latest changes pass CI workflows for testing and linting
• I have made corresponding changes to the documentation

[nicole-obrien]

As discussed on the call heres the main improvements to make:

• Lets make it so that we are not converting anything until we actually call the send function, so we can store all the params in the new transaction store and go backwards and forwards with ease.
• Add a network subject type to store network and address or just address as the subject and then store this in the recipient of the new transaction
• Add a layer 2 params to the new transaction and potentially a flag to say its layer 2. Then in another task we can easily use this data to go backwards and forwards in the send flow or to show the layer 2 details rather than the metadata as hex.
• Add a feature flag to make the network field readonly in the mainnet profiles but not in dev profiles.
• Add a Shimmer Testnet EVM network so its different to the Shimmer EVM

[nicole-obrien]

As per our review call:

• some of file names for constants don't match the constant names
• we should move the smart contract params to the params of the function to make it fully generic
• we should rename getLayer2Metadata to make it clear this is for a specific contract and call
• Ideally we should be adding the gas budget onto the amount when creating the output as this is an addition to the user defined amount which is used in the allowance field of the contract

[nicole-obrien]

LGTM!