docs: update taosbenchmark example includes

[danielclow]

use link relative to tdengine repo to align with all other includes

[gemini-code-assist]

Summary of Changes

Hello @danielclow, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on improving the consistency and maintainability of the documentation by standardizing how external example configuration files are referenced. It modifies the taosbenchmark documentation to use relative paths for including JSON examples, ensuring uniformity with other documentation sections and preventing potential issues with absolute path resolution.

Highlights

• Documentation Update: Updated the include paths for example configuration files within the taosbenchmark documentation.
• Path Consistency: Changed absolute include paths to relative paths to align with the standard linking convention used across the TDengine repository documentation.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the include paths for taosbenchmark example configuration files in the documentation. The changes replace what appear to be absolute paths with paths relative to the repository root. This is a good practice for documentation maintainability and portability. The changes are correct and consistently applied across all relevant include directives in the file. I find no issues with this change.