build: switch npm to yarn and resolve vulnerabilities

[eitjuh]

Hi folks 👋

We have discussed before whether to switch from NPM to Yarn, and we ended up not switching, because NPM was generally easier to debug.

Hereby I still make the suggestion to switch, because:

• faster
• adds the possibility to add resolutions to package.json, to resolve vulnerabilities in external dependencies

The following actually resolves the axios dependency.
We could directly ask ignite frontend team to update starport/vuex to update dependency @confio/relayer . That would fix it in a better way, but this is a temporary fix:

  "resolutions": {
    "**/@starport/vuex/@confio/relayer/axios": "0.21.2"
  },

[github-actions]

Visit the preview URL for this PR (updated for commit ee6979b):

https://emeris-app--pr1827-build-move-npm-to-ya-r5ludcud.web.app

_{(expires Mon, 13 Jun 2022 10:37:26 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

[Dawntraoz]

Nice idea! Code wise LGTM 💃🏼 Let's see what others say 💜

[pranaybaldev]

Not in support of the switch but don't feel too strongly about it (It'll be fine if we do). Can't we just use overrides?

'overrides' is only available in version 8.x.

[faboweb]

overrides in my experience don't work that well @pranaybaldev. Do you have good experiences with them?

[fl-y]

I also don't feel strongly about switching, however I remember @clockworkgr expressing that using npm made debugging easier. I'll be more comfortable with the PR with Alex's blessing