[Feature] Add Optional Time-Based Log Collection to Support Bundle Kit

Description

When investigating incidents (Root Cause Analysis), we often need to collect logs from a very specific time window (e.g., between 2:00 PM and 2:15 PM when the error occurred). Currently, the support bundle collects all logs, which can be a massive amount of data and makes it difficult and time-consuming to find the relevant information.

Solution

I would like to add an optional, opt-in feature to support-bundle-kit that allows users to collect logs within a defined time range. This would be a huge improvement for debugging and incident response. The feature should be opt-in, controlled by an environment variable (e.g., LOG_TIME_RANGE). When enabled, the kit should only fetch logs that fall within the specified time window. If the environment variable is not set, the behavior should remain exactly the same as before. This enhancement makes the tool much more powerful for targeted RCA without impacting its default behavior for users who don't need it.

The current alternative is to collect the full logs and then manually filter them, which is inefficient, especially in large clusters

No files, tests, or entry points are named. Start by tracing the existing log collection entry point and how environment variables are read; clarify the LOG_TIME_RANGE format, timezone and boundary behavior, then verify filtered collection and unchanged behavior when it is unset.