move from libolm to vodozemac due to deprecation

[k3-cat]

Preflight Checklist

• I could not find a solution in the existing issues, docs, nor discussions

Describe your problem

accroading to the olm repository:

All the client SDKs maintained by the Matrix core team
(matrix-rust-sdk, matrix-js-sdk, matrix-ios-sdk and matrix-android-sdk2) now
support vodozemac as their E2EE implementation - and the majority of apps built
on them (e.g. all variants of Element Web/Desktop/iOS/Android and Element X
iOS/Android) now use vodozemac.

As such as of July 2024, libolm is now officially deprecated - please do not
use it going forwards. The Matrix cryptography team sadly does not have
bandwidth to maintain both vodozemac and libolm, and all of our maintenance
effort will go into vodozemac.

Describe your ideal solution

replace libolm with vodozemac

Version

No response

Security requirements

https://soatok.blog/2024/08/14/security-issues-in-matrixs-olm-library/

Additional Context

• libolm is now deprecated. Nheko-Reborn/nheko#1786

• libolm is now deprecated. krille-chan/fluffychat#1258

• libolm deprecation and possible security vulnerablity quotient-im/libQuotient#780

• libolm is deprecated mautrix/go#262

• move from libolm to vodozemac due to deprecation  cinnyapp/cinny#1869

• Reconsider dependency on olm (GNOME Chatty)

• Add Matrix Rust crypto component (Thunderbird)