Add compatibility with Gnosis Chain

[AlexNi245]

At the moment, the Dm3 App only supports Dm3 Ethereum Mainnet. This issue aims to add support for .Gno domains stored on Gnosis Chain as well, enabling Genome users to use dm3 as their communication solution.

To identify Genome users, the reverse record has to be set on Genome so the provider can use the lookupAddress to determine the ENS name. If the ENS name ends with *.gno.eth, the user is a Genome user.

To add Genome compatibility, the following tasks have to be done:

• [x] Use a hardcoded mainnet provider for read requests to the Ethereum Chain instead of the Injected provider.
• [x] Refine SignIn so profiles can be created at Gnosis Chain instead of the Offchain resolver.
• [ ] Check if BE supports GNO domains that do not have address aliases.
• [ ] Store the resolver for GNO at a canonical registry on Ethereum Mainnet (Top Level Registry).
• [ ] Map gno domains to gno.eth in web3Provider obj

[steffenkux]

Is it gno.eth or gnosis.eth?

[steffenkux]

We should also add the UI tasks even if they are designated to mindfire.

[AlexNi245]

The following task are needed ui wise:

• [ ] Add profile creation dialog to the welcome screen if user is an GNO user and is connected with Gnosis Chain
• [ ] Maybe Gnosis related theming ?