[BugReport]Scan meeting up with an unresolved intent while its txn has committed and txn record has been gced.

**Describe the problem**

I scan with an iterator and I found an intent, then I sent `QueryTxnRequest` and `PushTxnRequest`. However, queried txn's state is `Aborted`, but actually I committed the txn.

**To Reproduce**

```
Session 1
begin;
create table t0 (id int primary key);
insert into t0 values (1);
insert into t0 values(2);
commit;
```

If possible, provide steps to reproduce the behavior:

1. Set up CockroachDB cluster
2. Send SQL above
3. Look at log file and debug keys --values.
4. See txn record deleted, intent on key 1 cleaned.

**Expected behavior**
I want to know hot to check txn of intent on key 2 whether is really committed.

**Additional data / screenshots**
Debug logs I will paste later.

If applicable, add screenshots to help explain your problem.

**Environment:**
- CockroachDB version [v20.1.17]
- Server OS: [Ubuntu 20.04]
- Client app [`cockroach sql`]

**Additional context**
What was the impact?

Add any other context about the problem here.

Jira issue: CRDB-31061