chore: improve error message when asset wasm is not allowlisted in playground

[sesi200]

Description

When we forget to allowlist the latest frontend canister wasm to the playground backend the error message is incomprehensible to users:

Error: Failed while trying to deploy canisters.
Caused by: Failed while trying to install all canisters.
Caused by: Failed to install wasm module to canister 'ii_integration_frontend'.
Caused by: install failed
Caused by: The replica returned a rejection error: reject code CanisterReject, reject message IC0503: Error from Canister ozk6r-tyaaa-aaaab-qab4a-cai: Canister called `ic0.trap` with message: Wasm is not whitelisted.
Consider gracefully handling failures from this canister or altering the canister to handle exceptions. See documentation: http://internetcomputer.org/docs/current/references/execution-errors#trapped-explicitly, error code None

New error message:

Error: Failed while trying to deploy canisters.
Caused by: Failed while trying to install all canisters.
Caused by: Failed to install wasm module to canister 'hello_frontend'.
Error explanation:
The frontend canister wasm needs to be allowlisted in the playground but it isn't. This is a mistake in the release process.
How to resolve the error:
Please report this on forum.dfinity.org and mention your dfx version. You can get the version with 'dfx --version'.

The removed .context("install failed") did not add any useful info.

Fixes SDKTG-418

How Has This Been Tested?

Tested manually.

Checklist:

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