feat: dfx deps: wasm_hash_url and loose the hash check

[lwshang]

SDK-1345

Description

Loose the constraint of wasm_hash :

• If the hash of downloaded wasm doesn’t match the provided hash, dfx deps won’t abort. Instead, it will print a warning message.
• The hash can still benefit wasm cache invalidation. If a downloaded wasm has the matching hash, dfx deps can skip the downloading.

Add another optional field wasm_hash_url in the pullable metadata.

• Providers like II can provide the hash through this URL instead of hard coding the hash directly.
• The hash of an alternative wasm module doesn’t have to be known beforehand. It can be modified later.
• For II, all flavors can be built in parallel. We will only need:
  • The PROD wasm has the wasm_url and wasm_hash_url in its pullable metadata.
  • The DEV build job pushes the wasm module and its hash through the URLs above.
  • The PROD and DEV build won’t intertwine with each other

How Has This Been Tested?

e2e tests / deps.bash

Checklist:

• The title of this PR complies with Conventional Commits.
• I have edited the CHANGELOG accordingly.
• I have made corresponding changes to the documentation.