stricter lint rules

[ivanhofer]

I want to share a few issues with the current code base:

• it should not be possible to build an appliaction if there are console.logs in the code (see issue)
  console.log are mosten used for debugging and often forgotten to remove. If there really is the case where we want to log something we can use console.info for that.
• enable formatting in CI. I sometimes format the code and I always need to revert the canges from packages I don't touch as I only care about my packages. Often it involves code I had written a few days or weeks ago for another PR so I have changes in my PR that should not be there. We once had a job that failed when the code was not formatted well, but we removed it. We should add a new CI job that formats the code and commits the canges to the branch instead of failing.
• someone always forgets to run npm i. It happens to often that I branch of from main, run npm i and have changes in package_lock.json. We should enforce that package_lock.json must be up2date.

[ivanhofer]

@inlang/team

[samuelstroschein]

1. yes, lint console logs
2. yes, in CI/CD autoformatting that commits = baba.
3. yes

[NiklasBuchfink]

I have come across every point and agree to take action. We should commit the code as clean as possible and without changes by running the current version.

[felixhaeberle]

@openscript agrees too, I have spoken with him already about these issues