Is it possible to migrate user password hashes to the latest hashing algorithm/configuration? E.g. - when a user logs in, could a bcrypt encrypted password be replaced with an argon2 encrypted password? - when a user logs in, could an argon2 encrypted password with

ARGON2_ITERATIONS=3

be replaced with one that is encrypted with

ARGON2_ITERATIONS=4

? The documentation [1] does explain that existing passwords will continue to work when switching to new configuration. But I'm interested in migrating passwords (on login) to the latest configuration. Is this possible? [1]: https://supertokens.com/docs/emailpassword/common-customizations/password-hashing/about#interoperable