fix: Update DateTime to TimestampSecond in information schema

[Copilot]

This PR updates the documentation for information schema tables to correctly reflect the timestamp data types as implemented in GreptimeDB core.

Problem

The documentation for INFORMATION_SCHEMA.PARTITIONS and INFORMATION_SCHEMA.TABLES incorrectly showed timestamp columns (create_time, update_time, check_time) as DateTime type, when they should be TimestampSecond type to match the actual implementation.

Changes

Updated the table schema documentation in both English and Chinese versions for:

• PARTITIONS table: create_time, update_time, check_time columns
• TABLES table: create_time, update_time, check_time columns

Files Updated

Nightly (current) documentation:

• docs/reference/sql/information-schema/partitions.md
• docs/reference/sql/information-schema/tables.md
• i18n/zh/docusaurus-plugin-content-docs/current/reference/sql/information-schema/partitions.md
• i18n/zh/docusaurus-plugin-content-docs/current/reference/sql/information-schema/tables.md

Version 0.17 documentation:

• versioned_docs/version-0.17/reference/sql/information-schema/partitions.md
• versioned_docs/version-0.17/reference/sql/information-schema/tables.md
• i18n/zh/docusaurus-plugin-content-docs/version-0.17/reference/sql/information-schema/partitions.md
• i18n/zh/docusaurus-plugin-content-docs/version-0.17/reference/sql/information-schema/tables.md

Example

Before:

| create_time      | DateTime |      | YES  |         | FIELD         |
| update_time      | DateTime |      | YES  |         | FIELD         |
| check_time       | DateTime |      | YES  |         | FIELD         |

After:

| create_time      | TimestampSecond |      | YES  |         | FIELD         |
| update_time      | TimestampSecond |      | YES  |         | FIELD         |
| check_time       | TimestampSecond |      | YES  |         | FIELD         |

This change ensures the documentation accurately reflects the timestamp resolution used in the information schema implementation as corrected in GreptimeTeam/greptimedb#7004.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• googlechromelabs.github.io
  • Triggering command: node install.mjs (dns block)
• https://storage.googleapis.com/chrome-for-testing-public/137.0.7151.119/linux64/chrome-headless-shell-linux64.zip
  • Triggering command: node install.mjs (http block)
• https://storage.googleapis.com/chrome-for-testing-public/137.0.7151.119/linux64/chrome-linux64.zip

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Update docs for fix: incorrect timestamp resolution in information_schema.partitions table</issue_title>
<issue_description>A document change request is generated from GreptimeTeam/greptimedb#7004</issue_description>

<agent_instructions>Change all DateTime type in tables of information schema to TimestampSecond type. Not only the partitions table. Update 0.17 and nightly docs, for both English and Chinese.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

Fixes #2145

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[cloudflare-workers-and-pages]

Deploying greptime-docs with    Cloudflare Pages

Latest commit:	f991a0e
Status:	✅  Deploy successful!
Preview URL:	https://76d947c1.greptime-docs.pages.dev
Branch Preview URL:	https://copilot-fix-e56f0bb6-373d-47.greptime-docs.pages.dev

View logs

[nicecui]

Does the content need to be applied to 0.17?