feat: [OI-204] vite migration

[mmoio]

• Remove craco dependencies and configuration
• adds vite dependencies and configuration
• refactored envs to work with vite
  • Replaces REACT_APP with VITE as env prefixes
  • removes env-var and use vite import.meta

[sebbalex]

Env file should respect the short environment names. This is mostly due to CIs which use this mapping to run trough envs.
So, I suggest to rename back .env.production to .env.prod and .env.development to .env.dev

[mmoio]

Env file should respect the short environment names. This is mostly due to CIs which use this mapping to run trough envs. So, I suggest to rename back .env.production to .env.prod and .env.development to .env.dev

I'should ve explained this changes better in the pr description, but vite uses some defaults when loading env files, some documentation regarding this argument in this page https://vite.dev/guide/env-and-mode. One of this default behaviours is loading a .env.development in a dev environment, and .env.production when building.
I will need to make some changes regarding the uat environment as well creating a custom mode in the future,.

[mmoio]

Env file should respect the short environment names. This is mostly due to CIs which use this mapping to run trough envs. So, I suggest to rename back .env.production to .env.prod and .env.development to .env.dev

For simplicity sake, I've changed back the environment files back to the original names, so to keep the pipeline environments coherent with the other parts of the project.
The only remaining change is renaming .env.local to .env.development, since is the one loaded by default by vite during development. A file .env.local is instead always loaded by vite and the defined variables in this file are overridden only if there is a more specific env file is loaded

[sebbalex]

Env file should respect the short environment names. This is mostly due to CIs which use this mapping to run trough envs. So, I suggest to rename back .env.production to .env.prod and .env.development to .env.dev

For simplicity sake, I've changed back the environment files back to the original names, so to keep the pipeline environments coherent with the other parts of the project. The only remaining change is renaming .env.local to .env.development, since is the one loaded by default by vite during development. A file .env.local is instead always loaded by vite and the defined variables in this file are overridden only if there is a more specific env file is loaded

Thanks for the clarification, now I have a more comprehensive view.
We can keep .env.development for local environment, since it is a local development file it doesn't need to have specific naming.
We should fix .env.dev because of its conflicts inside.
And eventually, we can think to have a .env.local file to gather all the common variables among different environment in it.

Here you can find the deployment pipeline which will build and ship the frontend stuff.

This line will load the environment from matrix (which it can be one from "dev|uat|prod", line 17) and build the app:
export $(grep -v ^# .env.${{ github.event.inputs.environment }} | xargs) && yarn build