Remove force rust crypto migration

[MarcWadai]

fixes #1096

Description

This commit is a revert of this PR on element side: matrix-org/matrix-react-sdk#12630

Before

• Force crypto migration on every new login/account and active/existing session

After

• Crypto migration on new login and account (if feature_rust_crypto is true in config)
• For existing account, the migration will happen depending on the value of the rollout. We need to activate feature_rust_crypto in order to use the rollout. It means that during the roll out, if a legacy user logout and login again, he will be automatically migrated even if the rollout phase is set to 0.

[odelcroi]

j'ai du mal à voir le lien entre le retablissement de cette fonction et le but de la PR, n'est-ce pas un résidu d'un autre commit?

[MarcWadai]

Cette méthode est utilisé dans le fallback libolm, qui a donc été supprimé lors du clean pour laissé que la crypto rust. Cf MatrixClientPeg.ts :

        // fall back to the libolm layer.
        try {
            // check that we have a version of the js-sdk which includes initCrypto
            if (this.matrixClient.initCrypto) {
                await this.matrixClient.initCrypto();
                this.matrixClient.setCryptoTrustCrossSignedDevices(
                    !SettingsStore.getValue("e2ee.manuallyVerifyAllSessions"),
                );
                await tryToUnlockSecretStorageWithDehydrationKey(this.matrixClient);
                StorageManager.setCryptoInitialised(true);
            }
        } catch (e) {
            if (e instanceof Error && e.name === "InvalidCryptoStoreError") {
                // The js-sdk found a crypto DB too new for it to use
                Modal.createDialog(CryptoStoreTooNewDialog);
            }
            // this can happen for a number of reasons, the most likely being
            // that the olm library was missing. It's not fatal.
            logger.warn("Unable to initialise e2e", e);
        }