feat: Deprecate --lock-write flag

[bartlomieju]

This commit deprecates --lock-write flag by removing it from
the help output and printing a warning message when it's used.

Users should use --frozen=false instead which was added
in #24355.

Towards #24167.

[pihentagy]

Nice, but --lock-write is still promoted in deno 1.45.5 when it figures out the source has changed:

pihentagy@dell:~/prg/example-project-for-zephyr$ deno cache --reload https://raw.githubusercontent.com/pihentagy/whatever
error: Integrity check failed for remote specifier. The source code is invalid, as it does not match the expected hash in the lock file.

  Specifier: https://googleapis.deno.dev/v1/sheets:v4.ts
  Actual: 28e9ab0ccbaac84b5a1f75f04aa361286e45f1aad864065516cc2c63ffdf89d2
  Expected: a1c80381d2dd3a74d1fd80f36e3f3a52b4945411904ca24eadd3a392e5bf8d0b

This could be caused by:
  * the lock file may be corrupt
  * the source itself may be corrupt

Use the --lock-write flag to regenerate the lockfile or --reload to reload the source code from the server.