`package-lock.json` changes depending on `wasp build`, `wasp clean` and `wasp compile`

[sodic]

Version: 0.19.2

Running wasp clean, wasp build or wasp compile (directly or through wasp start) changes the user's package.json. This was probably caused by #3130.

It's a problem because:

• Wasp seems unstable.
• User's can't use their package.json files normally.
• This might be causing our CI randomly to fail on example apps without much info (check waspello in this run), commiting the package.json after running wasp compile usually fixes this (check waspello in this run). I'm not sure this is the cause though, the CI logs suggest it's something else.

#3163 might solve a part of the problem but I'm not sure it's going to solve the entire problem.

[FranjoMindek]

I've encountered the same thing.
Ephemeral tests fail two random example app tests: #3465