Streamline code styles

[webbertakken]

Changes

• Make ESLint setup a bit more robust
• Uninstall husky hooks

Checklist

• Read the contribution guide and accept the code of conduct
• Readme (updated or not needed)
• Tests (added, updated or not needed)

[github-actions]

[codecov-commenter]

Codecov Report

Merging #384 (9cc66a4) into main (4be5d2d) will not change coverage.
The diff coverage is 66.66%.

❗ Current head 9cc66a4 differs from pull request most recent head 1bf138d. Consider uploading reports for the commit 1bf138d to get more accurate results

@@           Coverage Diff           @@
##             main     #384   +/-   ##
=======================================
  Coverage   54.69%   54.69%           
=======================================
  Files          62       62           
  Lines        1918     1918           
  Branches      316      316           
=======================================
  Hits         1049     1049           
  Misses        865      865           
  Partials        4        4           

Impacted Files	Coverage Δ
src/model/android-versioning.ts	100.00% <ø> (ø)
src/model/build-parameters.ts	95.34% <ø> (ø)
src/model/cli/cli-functions-repository.ts	43.75% <ø> (ø)
src/model/cli/cli.ts	31.34% <ø> (ø)
src/model/cloud-runner/cloud-runner.ts	79.31% <ø> (ø)
...ner/providers/aws/aws-cloud-formation-templates.ts	14.28% <ø> (ø)
.../model/cloud-runner/providers/aws/aws-job-stack.ts	9.52% <0.00%> (ø)
...odel/cloud-runner/providers/aws/aws-task-runner.ts	8.03% <ø> (ø)
src/model/cloud-runner/providers/aws/index.ts	17.50% <ø> (ø)
src/model/cloud-runner/providers/k8s/index.ts	12.00% <ø> (ø)
... and 30 more

[davidmfinol]

I get this warning:

warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.

Since we already yarn.lock, should we remove the package-lock.json file?

[webbertakken]

I get this warning:

warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.

Since we already yarn.lock, should we remove the package-lock.json file?

Indeed. I've removed the json file again and created a test so it's not created again in the future.