Influxdb3: Core and list tokens

[jstirnaman]

Closes #6022 #6021
Part of #5966

Add reference and guides for listing tokens using CLI and API
Update ref and guides for resource token syntax
Add examples, placeholders
Misc. fixes
WIP: added node.js script to generate docs from influxdb3 CLI help output. Partially works - not for all commands due to differences in help structure and headings.

[Copilot]

Pull Request Overview

This PR enhances the InfluxDB 3 documentation by adding and updating reference guides and examples for listing and creating tokens via the CLI and HTTP API for both Core and Enterprise editions. Key updates include:

• New pages and examples for the "show tokens" and "create token" CLI commands with various output formats and detailed SQL query usage.
• Updates to admin and resource token documentation to improve clarity and consistency in token permission examples.
• Minor textual and formatting fixes throughout the documentation to align with the new token syntax and usage guidelines.

Reviewed Changes

Copilot reviewed 19 out of 19 changed files in this pull request and generated 1 comment.

File	Description
content/shared/v3-enterprise-get-started/_index.md	Updated example explanations for system token permissions.
content/shared/influxdb3-cli/*	Added and updated examples for listing tokens and databases, including output to Parquet.
content/influxdb3/enterprise/*	Updated and expanded examples for creating tokens with fine-grained permissions and listing tokens via CLI and HTTP API.
content/influxdb3/core/*	Introduced new reference pages mirroring the enterprise guides for the Core edition.

Comments suppressed due to low confidence (2)

content/shared/influxdb3-cli/create/token.md:9

• [nitpick] Consider clarifying the placeholder '' to indicate the available subcommands (e.g., '--admin', '--permission') so that users understand what to replace it with.

influxdb3 create token <COMMAND> [OPTIONS]

content/influxdb3/enterprise/create/token.md:29

• [nitpick] Ensure that the token variable name 'AUTH_TOKEN' is used consistently across all examples; if an admin token is required in some examples, update the description accordingly.

--header "Authorization: Bearer AUTH_TOKEN"