fix(cli): catch all possible errors thrown from proper-filelock

[pimlie]

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Ref: #5324

Although I could have expected it maybe, its not really documented that proper-lockfile also throws errors when it cant release a lock. This pr should fix that behaviour by wrapping any code which originates from proper-lockfile in a try/catch and warn when an error was thrown.

The only time a lock should result in a Nuxt Fatal Error is when a lock with the same id already exists.

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly. (PR: #)
• I have added tests to cover my changes (if not applicable, please state why)
• All new and existing tests are passing.

[pi0]

Nice attempt @pimlie 👍

[codecov-io]

Codecov Report

Merging #5347 into dev will increase coverage by 0.06%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##              dev    #5347      +/-   ##
==========================================
+ Coverage   95.66%   95.72%   +0.06%     
==========================================
  Files          74       74              
  Lines        2513     2529      +16     
  Branches      639      641       +2     
==========================================
+ Hits         2404     2421      +17     
+ Misses         92       91       -1     
  Partials       17       17

Impacted Files	Coverage Δ
packages/utils/src/locking.js	100% <100%> (ø)	⬆️
packages/vue-renderer/src/renderer.js	92.07% <0%> (+0.49%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3c50876...c713b3f. Read the comment docs.