[BUG] Using AutoFill on a Basic authentication popup while the database is still locked returns "401 Unauthorized"

Checks

• I have read the FAQ section, searched the open issues, and still think this is a new bug.

Describe the bug you encountered:

The steps to reproduce are as follows:

1. Load a webpage which requires Basic auth using Firefox or Chrome
2. The Basic auth popup appears, select the username field and then the option to aufill with Kepass2Android (using the long press popup menu or the button in GBoard)
3. Select the desired credential set
4. The auth popup gets autofilled and disappears, the page starts loading but return a "401 Unauthorized" error.
5. Reloading or closing and reopening the page asks for the credentials again.
6. Now that the databse is already unlocked the login works as expected.

Note that unlocking the databse before loading the page makes the authentication work correctly right from the first try.

Describe what you expected to happen:

The login should work as expected without needing to closing or reloading the page a second time.

What version of Keepass2Android are you using?

1.09e-r7

Which version of Android are you on?

12

No file or test is named. First reproduce the Basic-auth and KeePass2Android autofill flow on Android 12 with the database locked, then trace the authentication and autofill handling involved in the first request. Done means the initial authentication succeeds without reloading or reopening the page.