Expected Behavior

TOTP to continue to work as it did in 2.3.4 showing RFC6238 settings from older entries

Current Behavior

TOTP gives 1 second 1 digit 'custom' codes.
when you go into the setup TOTP options, and set it to default RFC6283 it still shows your key, however when you click ok and then try and view the TOTP again it now shows 6 digits with 1 second time step, and setup now has a blank key and is back to 'use custom settings'

I was able to clear all otp and TOTP attributes, save, close keepassXC completely, then when I went back to the entry I was able to set it up new and it worked.

Possible Solution

ether always default to the RFC settings if no up to date settings are found, or migrate the otp:key= attribute to the current TOTP Seed and TOTP Settings attributes

Steps to Reproduce

1. open any database with an entry made with keepass and a TOTP with KeeOtp plugin
2. attempt to interact with TOTP show/setup

Context

I have Entries with totp settings created in keepass with KeeOtp's setting otp:key= attribute.
in KeepassXC 2.3.4 these entries work correctly. In 2.4 beta these entries now only give a code of one digit for one second, and any attempts to use setup TOTP do not work to fix the entry

Debug Info

KeePassXC - Version 2.4.0-beta1
Build Type: PreRelease
Revision: 42cfe01

Libraries:

• Qt 5.12.0
• libgcrypt 1.8.4

Operating system: Windows 10 (10.0)
CPU architecture: x86_64
Kernel: winnt 10.0.15063

Enabled extensions:

• Auto-Type
• Browser Integration
• SSH Agent
• KeeShare (signed and unsigned sharing)
• YubiKey