Use package-lock.json of the repo

[atxr]

Currently, when building the website (both prod and dev mode), we are using npm install and regenerating a new package-lock.json.
There is no point of pushing the package-lock.json on the repo if we override them when building.
We should change all the occurrences of npm install by npm ci (clean install) which use the current package-lock.json instead of overriding it.
Hence, we can lock a version of a package we use if needed, and we won't have any version issue when building the app at different places.

[ctmbl]

That's right! I'll add this one to the v0.2.0 milestone!