1. Proposed title of this feature request

The must-gather should maintain session activity to prevent accessTokenInactivityTimeout failures

2. What is the nature and description of the request?

The request addresses a conflict between long-running `must-gather` operations and strict security configurations. Currently, if `accessTokenInactivityTimeout` is set to a short duration (e.g., 300s) and `must-gather` runs longer than that limit, the operation fails with "Unauthorized" errors, leading to incomplete data collection.

The request is for the oc adm must-gather client to implement a "keep-alive" mechanism (heartbeat) or token refresh logic that signals activity to the API server, ensuring the session remains valid for the duration of the diagnostic run.

3. Why does the customer need this? (List the business requirements here)

• Regulatory Compliance: Customers in highly regulated sectors (Banking, Government, PCI-DSS environments) are mandated to enforce short session timeouts (e.g., 5-10 minutes).

• Security Posture: Customers currently have to violate their own security policies (relaxing the timeout) just to collect logs for support, which creates a security gap and requires complex change management approvals.

• Operational Stability: Ensures that standard diagnostic tools work reliably in hardened environments without manual workarounds.

4. List any affected packages or components.

• Must-Gather