Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Currently when Windows Hello prompt appears and user clicks cancel, standard prompt will appear, and then when you close KeePass and try to open and unlock that database again Windows Hello prompt won't appear.
But sometimes user might misclick KeePass, in this case user wants to close Windows Hello prompt, but then user cannot use Windows Hello in secondary unlock attempt because this plugin doesn't allow user to do that.

Describe the solution you'd like
A clear and concise description of what you want to happen.
My suggestion would be adding an option for users to decide: users can choose to let this plugin disable Windows Hello when its being used once and failed, or for users like me would love to let plugin continue asking for Windows Hello regardless of the situation.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Or copy the Keepass2Android unlock mechanism, an option for users to decide whether Windows Hello unlock is only bound to Quick Unlock or to Master Password. When bound to Quick Unlock, users cannot use Windows Hello when KeePass is being locked (but not closed) and the first attempt failed. When bound to Master Password, in addition to how it works with Quick Unlock, user can also restore the functionality of Windows Hello unlock after restarting KeePass.
(I don't know why😂, I thought the first solution would be better)

Additional context
Add any other context or screenshots about the feature request here.