Re-think part of the app's routing architecture in terms of remix routing?

[PJColombo]

It would be better to refactor the contract descriptor screen, separating some of their views components to their own route, following remix routing idea and harnessing the nested routes concept where multiple routes match portions of an URL to render specific components forming a hierarchy.

A possible routing design:

• /contracts?q=<contract-address>: It renders the ContractSelectorScreen
• /contracts/<network-name-abbr>:<contract-address>/functions/<sig-hash>/describe: It renders the ContractDescriptorScreen.
• /contracts/<network-name-abbr>:<contract-address>/functions/<sig-hash>/test: It renders the TestModal

In regards of network-name-abbr, we would use abbreviations similar to Gnosis Safe's, e.g., gno, matic, eth, etc