[Adena] add support for GnoConnect (gnoweb)

[moul]

Update the Adena Wallet to detect and utilize the new gnoconnect:... metadata tags added to gnoweb-generated HTML. These metadata entries provide configuration details for seamless integration. Ideally, this should enable Adena to function on any testnet, as well as any devnet or localnet.

The wallet should parse the following <meta> tags present in the page's HTML:

<meta name="gnoconnect:rpc" content="127.0.0.1:26657" />
<meta name="gnoconnect:chainid" content="dev" />

Using these values, the wallet should recognize that the current webpage serves as a frontend for a Gno blockchain instance. We can envision the extension automatically including a "login" feature, such as checking if the current wallet has a balance. Ultimately, it will allow Adena to capture the current txlink, such as https://gno.land/r/demo/boards$help&func=CreateThread&bid=2, and intercept it to open the wallet window with a prefilled transaction. This will prevent redirection to the current gnoweb help page, which will remain the default for users without an installed gnoconnect wallet. We can also imagine additional features when someone opens a help page directly, such as adding a new "Run with Adena" option after the existing copy-paste transaction instruction.

Depends on #3609
Related with #2602
Related with #2799
Related with #3283
Related with onbloc/adena-wallet#302

[jinoosss]

Hi @moul ,

Adena can:

• parse the meta tag of gnoconnect and change the chain environment.
• generate a injection pop-up that reads the parameters of gnoconnect and txlink to execute a transaction.

I have a few questions:

1. What is the rule of generating a URL? I see the current one as https://gno.land/r/demo/boards$help&func=CreateThread&bid=2,
   but if Adena knows the rules for how URLs are reflected when parameters are entered into a transaction message, Adena can open a prefilled injection pop-up as soon as a txlink is opened.

2. When the txlink feature is extended (Extend txlink, ?help, and Wallet Connect to Support maketx run #3283),
   it would be most user-friendly if users could create txlinks in Adena (Morgan's comment). But I don't think it's user-friendly to directly modify the content of the script, therefore, I think it would be best if Adena provide a selection of pre-defined functions from the selected realms from the UI (with a dropdown modal), and generate the transaction message for a txlink for users. How do you think about this approach?

[moul]

Hey @jinoosss, please take a look at #3615 and let me know if you still have questions. If possible, ask them directly on #3615 if they are general to the specifications.