[BWA-187] Unable to generate codes for a URI with "%20" in it (theory). May not be properly imported to local Authenticator.

### Steps To Reproduce

1. In a Bitwarden entry, for the TOTP field value, place a value like:
2. otpauth://totp/USCIS%20myAccount:santaclaus@northpole.com?secret=OO6OMWAWMCTADIN7ZPSV7MEJFCF4X6CY&issuer=USCIS%20myAccount
3. ^^ Note: fake email, and random character secret string. Not actual values.
4. Sync Bitwarden on Android. Verify the URI is present in the entry
5. Authenticator app is syncing from Bitwarden
6. Open Authenticator
7. Search for the entry - won't be found
8. Return to Bitwarden. Edit the entry, leaving just the secret string of 32 characters removing the before and after parts.
9. Sync Bitwarden
10. Open Authenticator
11. Search for the entry - now found!

### Expected Result

My import to Bitwarden and then subsequent use of sync'd Authenticator doesn't generate this code. I have a theory it's the %20's in the supporting strings that aren't being taken account of by the Authenticator app.

This might be a problem if one exports codes from another code-only generator application to Authenticator, and this entry got dropped and isn't generating. I think that's what happened to me but difficult to prove without nuking my Authenticator local data.

### Actual Result

I'd expect correct generated codes for all secret strings.

### Screenshots or Videos

_No response_

### Additional Context

_No response_

### Build Version

Bitwarden 2025.7.2 ; Authenticator 2025.7.2

### What server are you connecting to?

US

### Self-host Server Version

_No response_

### Environment Details

Pixel 9a on the August release

### Issue Tracking Info

- [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.