fix: move-to-script-setup-and-fix-all-eslint-errors

Note: I'm actually quite certain that this MUST break SOMETHING, SOMEWHERE. It's just a matter of what exactly. However, for the benefit of cleaning up our codebase, and trying to gain some speed towards improving our product, I'd still want to push this forward (and if things break, the tests or PR should have covered it anyway)

Update: Actually now it's not just the homepage - everything should be resolved when you run npm run build

Reason for doing:

I can't stand the linting errors anymore
- Every time if I run npm serve, it takes super long + sometimes the UI is not interactive yet because it's still linting
it makes the code shorter/cleaner
I suspect that this is one of the reasons why our runners are sometimes failing - because this takes a lot of memory
I needed something simple and mindless to do - felt effective, even though it might not be important 😅

Changes like:

script setup
styles changed to tailwind

Testing:

Look at the list of files changed, and try out these actions (swaps/sends/looking at balance).
Generic testing and using all functionality on the website

Main testing that I have done:

✅ Connect/Disconnect wallet
✅ Swap
✅ Send
✅ Move
✅ Claim rewards
✅ Staking
✅ Unstaking (undelegating)
✅ Switching validator (found a small bug - fixing now)
✅ Portfolio page
✅ Asset page
✅ Settings modal

Scope:

Right now, it's 74 files - all related to the homepage. When trying to just run npm run dev, all eslint warnings are gone - the other pages still have plenty, but have to start somewhere...

EmerisHQ / demeris

fix: move-to-script-setup-and-fix-all-eslint-errors #1835