Do not require user interaction in tsh status when using hardware keys

[gzdunek]

As discussed in #20849, tsh status shouldn't require user interaction. Unfortunately, since that PR was merged, another remote call has been added that may prompt the user for touch/PIN.

I looked at other usages of onStatus and I believe all of them should be fine with this change. We probably don't need showing access lists to review after creating or dropping an access request.

However, the main reason I opened this PR is that the user is not even able to respond to the prompt:

grzegorz@mbp build % ./tsh status
Enter your YubiKey PIV PIN:
> Profile URL:        https://moon.cloud.gravitational.io:443
  Logged in as:       grzegorz.zdunek@goteleport.com
  Cluster:            moon.cloud.gravitational.io
...

This happens since #47091. We added there a "warm up" call (it prompts for touch/PIN) that ensures the key is ready before we initiate a gRPC dialing. That call receives a context, but unfortunately for tsh status it has a really short deadline - 750 ms, so the user is not even able to provide a PIN or touch.

[public-teleport-github-review-bot]

@gzdunek See the table below for backport results.

Branch	Result
branch/v14	Create PR
branch/v15	Create PR
branch/v16	Create PR
branch/v17	Create PR