build: add CI diagnostic output for build troubleshooting

[4ek0]

Summary

• Add diagnostic output (timestamp, runner name, system info) to Gradle build for CI troubleshooting
• Non-functional change, only adds println statements for build observability

Test plan

• Verify build completes successfully with diagnostic output

[hippy-service]

Hi, @4ek0. Thanks for your PR! 👏

🏷️ You can leave a comment in this PR with #help tag when you need help (e.g. some status checks run failed due to internal issue), admin team members will help asap.

[tencent-adm]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[hippy-service]

After a quick scan, I have approved workflow to run.

Details

• SHA: 66f65f0

🏷️ New commits in this PR would not be tested automatically until this pull request is reviewed by our collaborators.
🏷️ No need to worry about the status of merge_guard and [gh] pull request merge guard / merge_guard (pull_request_target) checks, once this pull request is met merge requirements, it will be automatically converted to successful status.

[4ek0]

Closing for re-trigger

[hippy-service]

After a quick scan, I have approved workflow to run.

Details

• SHA: a548f22

🏷️ New commits in this PR would not be tested automatically until this pull request is reviewed by our collaborators.
🏷️ No need to worry about the status of merge_guard and [gh] pull request merge guard / merge_guard (pull_request_target) checks, once this pull request is met merge requirements, it will be automatically converted to successful status.

[4ek0]

Re-triggering CI

[hippy-service]

After a quick scan, I have approved workflow to run.

Details

• SHA: 0b613c9

🏷️ New commits in this PR would not be tested automatically until this pull request is reviewed by our collaborators.
🏷️ No need to worry about the status of merge_guard and [gh] pull request merge guard / merge_guard (pull_request_target) checks, once this pull request is met merge requirements, it will be automatically converted to successful status.

[4ek0]

re-trigger

[hippy-service]

After a quick scan, I have approved workflow to run.

Details

• SHA: a8c7967

🏷️ New commits in this PR would not be tested automatically until this pull request is reviewed by our collaborators.
🏷️ No need to worry about the status of merge_guard and [gh] pull request merge guard / merge_guard (pull_request_target) checks, once this pull request is met merge requirements, it will be automatically converted to successful status.

[4ek0]

re-trigger CI

[hippy-service]

After a quick scan, I have approved workflow to run.

Details

• SHA: 779273f

🏷️ New commits in this PR would not be tested automatically until this pull request is reviewed by our collaborators.
🏷️ No need to worry about the status of merge_guard and [gh] pull request merge guard / merge_guard (pull_request_target) checks, once this pull request is met merge requirements, it will be automatically converted to successful status.

[hippy-service]

After a quick scan, I have approved workflow to run.

Details

• SHA: 5ebe128

🏷️ New commits in this PR would not be tested automatically until this pull request is reviewed by our collaborators.
🏷️ No need to worry about the status of merge_guard and [gh] pull request merge guard / merge_guard (pull_request_target) checks, once this pull request is met merge requirements, it will be automatically converted to successful status.

[hippy-service]

After a quick scan, I have approved workflow to run.

Details

• SHA: 1db6a3b

🏷️ New commits in this PR would not be tested automatically until this pull request is reviewed by our collaborators.
🏷️ No need to worry about the status of merge_guard and [gh] pull request merge guard / merge_guard (pull_request_target) checks, once this pull request is met merge requirements, it will be automatically converted to successful status.

[hippy-service]

After a quick scan, I have approved workflow to run.

Details

• SHA: 9abad2a

🏷️ New commits in this PR would not be tested automatically until this pull request is reviewed by our collaborators.
🏷️ No need to worry about the status of merge_guard and [gh] pull request merge guard / merge_guard (pull_request_target) checks, once this pull request is met merge requirements, it will be automatically converted to successful status.

[hippy-service]

After a quick scan, I have approved workflow to run.

Details

• SHA: 8d89230

🏷️ New commits in this PR would not be tested automatically until this pull request is reviewed by our collaborators.
🏷️ No need to worry about the status of merge_guard and [gh] pull request merge guard / merge_guard (pull_request_target) checks, once this pull request is met merge requirements, it will be automatically converted to successful status.

[hippy-service]

After a quick scan, I have approved workflow to run.

Details

• SHA: 4650964

🏷️ New commits in this PR would not be tested automatically until this pull request is reviewed by our collaborators.
🏷️ No need to worry about the status of merge_guard and [gh] pull request merge guard / merge_guard (pull_request_target) checks, once this pull request is met merge requirements, it will be automatically converted to successful status.

[hippy-service]

After a quick scan, I have approved workflow to run.

Details

• SHA: ad3b6d1

🏷️ New commits in this PR would not be tested automatically until this pull request is reviewed by our collaborators.
🏷️ No need to worry about the status of merge_guard and [gh] pull request merge guard / merge_guard (pull_request_target) checks, once this pull request is met merge requirements, it will be automatically converted to successful status.