Rewrite the frontend to React

[lubej]

Description

• changed frontend framework from Vue to React

Resolves #18

[rube-de]

As the issue mentions current best partices, maybe the react implementation can directly use v2 and implement SIWE like in the other PR.

[matevz]

As the issue mentions current best partices, maybe the react implementation can directly use v2 and implement SIWE like in the other PR.

SIWE is ideal for the frontend, but I'm not sure if we should also suggest using it in the backend.

[rube-de]

• When the user rejects the signing the Something went wrong blocks any further interaction => I think giving a way to the user to retry would be good
• When setting a new message, it also asks for the view call to read the message, but still isn't revealing it and you need to click tap to reveal
  => it can be confusing for the user why he needs to sign more than a tx when setting a message, I think it would better to have the signed view call only when the user want to reveal the message
• (nice to have) I think it would be nice if the account was already connected, the user keeps being connected when refreshing the page, most dapps don't lose the connected account. (is maybe a feature of Rainbowkit etc)

[lubej]

• When the user rejects the signing the Something went wrong blocks any further interaction => I think giving a way to the user to retry would be good
• When setting a new message, it also asks for the view call to read the message, but still isn't revealing it and you need to click tap to reveal
  => it can be confusing for the user why he needs to sign more than a tx when setting a message, I think it would better to have the signed view call only when the user want to reveal the message
• (nice to have) I think it would be nice if the account was already connected, the user keeps being connected when refreshing the page, most dapps don't lose the connected account. (is maybe a feature of Rainbowkit etc)

All the points were addressed in e8c62d6

The reason for not using Rainbowkit is simple, as far as I know currently there is no "sapphire wrapper" support for viem-v2, hence no support for signed queries. Should also be migrated in #21

[rube-de]

LGTM now.
Only thing I noticed is, that with the current contract in env.development, I could also read the message from an account which wasn't the author. Doing fresh deploy of the contract and using it, it worked then as expected.

[lubej]

@matevz can we merge this PR? And hold off with #16, or would you rather merge #16 first.