attempt to use current timezone when checking api key expiry

[MoralCode]

the collectoss github api-keys CLI output shows the key expiry time, but it defaults to using UTC. Having it be shown in local time would make it more helpful for people who regularly use it.

[iGufrankhan]

@MoralCode
When I run:
collectoss github api-keys
inside the Docker container, the output still shows:
07:08 PM UTC (UTC+0000)

i think
After checking further, the container itself is configured to use UTC (datetime.now().astimezone() also returns UTC), so astimezone() is behaving as expected for the container environment.

Could you clarify the expected behavior for this issue?
Should the CLI display the host machine's local timezone even when running inside Docker?

The CLI uses datetime.fromtimestamp(...).astimezone(), which converts to the local timezone of the environment where Python is running. Since I'm running CollectOSS in Docker and the container timezone is UTC, it correctly shows UTC. Did you intend "local time" to mean the host machine's timezone even when running inside Docker?

[MoralCode]

Yeah, if everything is set up for a dynamic timezone, i think just mounting /etc/timezone or setting TZ env var in the container should be fine.

Instance hosts shoupd have control over whether CollectOSS runs in UTC or some other timezone

[iGufrankhan]

That makes sense. Since the CLI already uses astimezone(), I'll look into configuring the container to respect the host timezone for ex via the TZ environment variable or /etc/timezone rather than changing the Python code.