fix: Consider JS optimizations suggested by Lighthouse

[janmichek]

Description

fixes #775

Demo

This issue was more of exploration of the topic what we can do in regards of optimization nut I was able to increase the score.
I implemented the nuxt-booster which is doing som lazy loading under the hood.
I also optimized the SVG icons.
There is more potential to optimize (listing for further improvements)

• off load from Main thread (using nuxt booster or partytown) (Sentry, plausible)
• lazy load, off load or replace monaco editor as it is a biggest dependency
• creating dedicated backend will also help to reduce waiting time as there is a lot of data gluing

Anyway this attempt helped to increase the score
You can compare the result with some other PR without optimization
https://pagespeed.web.dev/analysis/https-pr-811-aescan-stg-service-aepps-com/3ko3nump6i?form_factor=mobile
https://pagespeed.web.dev/analysis/https-pr-801-aescan-stg-service-aepps-com/lb66xs5x03?form_factor=mobile

I also tested with Unlighthous which crawls more pages than just mainpage

Checklist:

• I have read and followed the Contributing Guide

[github-actions]

Deployed to https://pr-801-aescan.stg.service.aepps.com and https://pr-801-aescan-testnet.stg.service.aepps.com

[michele-franchi]

LGTM

[Liubov-crypto]

LGTM