[Bugfix] (grpc): improve GetServerInfo response consistency and accuracy

[pacoxu]

Purpose

Try to fix 2 TODOs.

• Use single time.time() for last_receive_timestamp and uptime_seconds to avoid drift between the two values
• Report actual pause state via self.async_llm.is_paused instead of hardcoded False

Test Plan

grpc server endpoint support was added in #30190.
cc @CatherineSue @njhill

Test Result

---

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• The test plan, such as providing test command.
• The test results, such as pasting the results comparison before and after, or e2e results
• (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
• (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

[gemini-code-assist]

Code Review

The pull request effectively addresses two outstanding TODOs in the GetServerInfo gRPC endpoint. It significantly improves the consistency and accuracy of the server's reported state by ensuring that last_receive_timestamp and uptime_seconds are derived from a single timestamp capture, thereby preventing potential time drift. Additionally, the server's pause state is now correctly reported using the actual self.async_llm.is_paused status, rather than a hardcoded False value.

[CatherineSue]

LGTM

[njhill]

Thanks @pacoxu. I'm guessing last_receive_timestamp is meant to be something different though (ie not just current time). Perhaps you could leave a TODO comment there

[pacoxu]

Thanks @pacoxu. I'm guessing last_receive_timestamp is meant to be something different though (ie not just current time). Perhaps you could leave a TODO comment there

Added a comment. Thanks for reviewing.