Crypto-wasm asset changes hash between builds

### Steps to reproduce

1. Build element-call.
2. Note the hash for the crypto-warm asset.
3. Change something in element-call but keep the same crypto-wasm version.
4. Build element-call again.
5. Check the crypto-wasm asset again to see what hash was allocated.
6. See that it is different than before.

### Outcome

#### What did you expect?

The asset hash would depend on the npm version. So, if the npm version hasn’t changed then the asset name would be the same and there is some chance that the browser will have cached the asset.

#### What happened instead?

The asset hash changed even though the npm version was the same.

### Operating system

_No response_

### Browser information

_No response_

### URL for webapp

_No response_

### Will you send logs?

No