Do not send "assume role" usage event when dropping access request

[gzdunek]

Closes #42484

To fix the issue, I separated methods for assuming and dropping requests. We never assume and drop a request at the same time, so I think this change will make this API easier to use. Let me know what you think about it.

While I was there, I also removed cluster.connect checks. Each of these calls is wrapped in retryWithRelogin in UI and clusters.AddMetadataToRetryableError in tshd.
If the cluster is not connected, we should ask the user to log in, rather than fail silently.

After that I removed some methods completely, as they only passed calls to tshd.

[ravicious]

  const [deleteRequestAttempt, runDeleteRequest] = useAsync(() =>
    retry(() =>
      ctx.tshd.deleteAccessRequest({
        rootClusterUri,
        accessRequestId: requestId,
      })
    )
  );

web/packages/teleterm/src/ui/DocumentAccessRequests/ReviewAccessRequest/useReviewAccessRequest.ts:74:7 - error TS2739: Type 'CloneableUnaryCall<DeleteAccessRequestRequest, EmptyResponse>' is missing the following properties from type 'Promise<FinishedUnaryCall<DeleteAccessRequestRequest, EmptyResponse>>': catch, finally, [Symbol.toStringTag]

74       ctx.tshd.deleteAccessRequest({
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
75         rootClusterUri,
   ~~~~~~~~~~~~~~~~~~~~~~~
76         accessRequestId: requestId,
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
77       })
   ~~~~~~~~

  web/packages/teleterm/src/ui/DocumentAccessRequests/ReviewAccessRequest/useReviewAccessRequest.ts:55:17
    55     <T>(action: () => Promise<T>) => retryWithRelogin(ctx, clusterUri, action),
                       ~~~~~~~~~~~~~~~~
    The expected type comes from the return type of this signature.

I guess we forgot to implement catch and finally on the cloneable client? 😩 Or just maybe it's a matter of adding relevant types. This whole time I've assumed they were implemented in terms of then. 🤷

Anyway, it's something we should tackle down the road.

[gzdunek]

No, we didn't not forget.

protobuf-ts type exposes only .then - this concept is called thenable https://masteringjs.io/tutorials/fundamentals/thenable.

To simplify this call we could remove await:

  const [deleteRequestAttempt, runDeleteRequest] = useAsync(() =>
    retry(async () =>
      ctx.tshd.deleteAccessRequest({
        rootClusterUri,
        accessRequestId: requestId,
      })
    )
  );

but I wanted the attempt to be of type Attempt<void>, since we are not interested in the response anyway.

[public-teleport-github-review-bot]

@gzdunek See the table below for backport results.

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