Enhance/Expand "User Credentials"/"Local Credentials"

Currently, in "File" > "My account settings" > "User credentials" (or "Local credentials"), exists a limited set of entries intended for the user's unique credentials. Right now there is:

• My personal credentials
• My privileged account
• My personal SSH key

And, while "My personal SSH key" can only be a SSH key, the other two options can be:

• API key
• Certificate (X.509)
• Custom
• One-time password (OTP)
• Password list
• Secret
• SSH key
• Username and password

In environments where a user has multiple accounts (many reasons for this, such as separation of privileges, or regulatory requirements stating that certain user types cannot login to certain system types, etc), this is quite limiting. Not only could a user foreseeably require multiple different "personal credentials" as well as "privileged accounts", but each of those likely also have associated API keys, certificates, secrets, SSH keys, OTP entries, etc.

Existing documentation refers to the fact that these objects are stored in a Credentials.rdt file (https://docs.devolutions.net/rdm/commands/file/my-account-settings/my-personal-credentials/). Possibly, as a way to address this limitation, I think it would be good to see something like the User credentials section expanded to behave more like a typical vault, which is limited to Credential-type entries, and sessions in local datasources/advanced datasources (with local overrides)/etc, may perform an action such as setting the credentials to "Linked (Credential Vault)".

Something else I would like to see added (separately/independently of the above) is a check on-launch to see whether or not the user has got a "personal credential" and/or a "privileged account" set (ideally, there should be options to set the check for one or the other, or both). I imagine this check working a similar way to when the group policy for "Force login" is set -- if it is enabled without also configuring either "Force Windows credentials and currently logged on username and domain" or "Force application password", then on first launch, the user is prompted which of these two options they would like to use (and to set a password in the instance of application password).