Use olm WASM with content hash on web in production

Summary:
This differential fixes an urgent Linear issue: https://linear.app/comm/issue/ENG-5895/web-notification-decryption-error. Production web builds will use
olmFilename variable with content hash provided by the keyserver. Development builds will use default olm.wasm filename.

Test Plan:

1. Clear all cache files for localhost:3000/comm. This step is necessary since production builds might have used olm WASM from cache populated by dev builds.
2. Builds production web app.
3. Ensure that notifications are encrypted (MariaDB console) and correctly decrypted on the keyserver.

Reviewers: michal

Reviewed By: michal

Subscribers: ashoat, tomek

Differential Revision: https://phab.comm.dev/D10047