Use rust crypto instead of libolm

[ajbura]

Description

Fixes #1869

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[marekvospel]

@ajbura I took a look at why this error was ocurring. Found this npm/cli#4828. Regenerating the package-lock.json as advised has worked. Also vite-plugin-top-level-await needs to be updated to v1.4.2. (see Menci/vite-plugin-top-level-await#52)

Also looking at fe4d0be, there are some duplicate lines, so changes of that commit might need to be revised.

I have done these changes (https://github.com/marekvospel/cinny/commits/js-sdk-v34/), and the build started passing. (I am seeing a lot of IndexedDBStore failure, degrading to MemoryStore TypeError: this.db is undefined errors in the console though, so there might be more needed to get this to work correctly)

I hope this isn't too bold move from me. Since this is a security concern, I'd love this to be resolved as fast as possible, and this PR seemed stale. Feel free to contact me if there is anything I can help with 😉 @marek:vospel.cz

[notramo]

Why are new features added (e.g. pinned messages) while there are open security vulnerabilities? Is there a particular blocker for this refactor?

[ajbura]

Adding rust crypto needs all crypto related features to be tested, this PR is waiting for #1988 so related work can be shared.