M5 - Make mvp demo mpa(multi-page application)

[hanabi1224]

Summary of changes
Changes introduced in this pull request:

• Converts the single-page demo to multi-page so that more functionalities can be integrated, e.g. readme, send transaction, etc.
• Integrate with tailwindcss
• Make chrome extension without sandboxing (requires chrome canary for now)
• Render project readme.md on index page
• Create page skeleton for graphql demo
• Build chrome extension mv2 for chrome stable / edge and firefox
• Instructions on using the extension chrome canary/stable, edge and firefox

Reference issue to close (if applicable)

Closes

Other information and links

[codecov-commenter]

Codecov Report

Merging #205 (6deb15d) into main (82ffe52) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #205   +/-   ##
=======================================
  Coverage   85.25%   85.25%           
=======================================
  Files         101      101           
  Lines        4341     4341           
=======================================
  Hits         3701     3701           
  Misses        640      640           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 82ffe52...6deb15d. Read the comment docs.

[willemolding]

Any idea how much effort would be required to support Firefox? As I understand:

• Firefox extensions don't support manifest v3 so we would need to switch to v2
• I think Firefox supports unsafe-wasm-eval in extensions (need to confirm this)

There is no Chrome Canary for Linux, so if we continue down the current path we will only support non-linux chrome users.

[hanabi1224]

@willemolding

That's a good suggestion, I've added extension mv2 support.

so we would need to switch to v2

v2 cannot be published to chrome extension store anymore, which is the deal-breaker

There is no Chrome Canary for Linux

According to posts in the Chrome mail list, this is a bug fix and will roll out to chrome stable soon. MV3 is required for publishing to the Chrome extension store, which is the plan made by our partner

[creativcoder]

Tested on my local for v2 and as a web page. Looking great!