[PM-27159] Inconsistently, RFC 6238 generations are not replaced in the UI when PT30S elapses, until the entrant is re-accessed.

### Steps To Reproduce

1. Create an item with a TOTP key:

~~~sh
#!/usr/bin/env sh
bw create item "$(jq -n \
--arg name "Example Service" \
--arg totp "otpauth://totp/Example:user@example.com?secret=JBSWY3DPEHPK3PXP&issuer=Example&algorithm=SHA1&digits=6&period=30" \
'{type:1, name:$name, login:{username:$username, password:$password, totp:$totp}}')" \
--session "$BW_SESSION"
~~~

That's merely an example. It's not prescriptive.

1. Visit it in `com.x8bit.bitwarden/.MainActivity`.

1. Wait PT30S.

### Expected Result

The generated code should have been replaced.

### Actual Result

The code did not refresh, until I closed, then re-accessed, the vault entrant.

### Screenshots or Videos

This was infeasible when it occurred, per [`community.bitwarden.com/t/317/15`](https://community.bitwarden.com/t/option-to-allow-screenshots/317/15?u=rokejulianlockhart).

### Build Version

> ~~~ini
> versionName=2025.9.1
> versionCode=20742
> ~~~

### What server are you connecting to?

US

### Server Version

> ~~~YAML
> Server version: 2025.9.2
> ~~~

### Environment Details

#### Device

> ~~~YAML
> [ro.product.brand]: [Fairphone]
> [ro.build.product]: [FP5]
> ~~~

#### OS Version

> ~~~YAML
> [ro.build.version.release]: [15]
> [ro.build.display.id]: [FP5.VT28.C.042.20250623]
> ~~~

### 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.