Please help check IO Capability Handling

Hi Bumble Team,

I’ve been using the `on_authentication_user_confirmation_request` method in `device.py` and noticed that some IO capability combinations currently result in `na` (not available) methods, which may be incomplete.
For example,
- when `peer_io_capability` is `KEYBOARD_ONLY` and `local_io_capability` is `DISPLAY_YES_NO`, the method is currently marked as `na`, but based on the IO capability logic, it should be: `display_number` for the local device and `passkey_entry` for the remote device

Do you have any plans to implement these missing cases?

Additionally, I found a few combinations that seem to be incorrectly mapped:
For example,
- when both `peer_io_capability` and `local_io_capability` are `DISPLAY_ONLY`, the method should be `auto_confirm`, not `display_auto_confirm`.
- when `peer_io_capability` is `NO_INPUT_NO_OUTPUT` and `local_io_capability` is `DISPLAY_ONLY`, the method should also be `auto_confirm`, not `confirm`.

Could you please help verify these mappings and let me know if any updates are planned?

Thanks for your time and support!

Best Regards,
Can Wang