Fix link checker for fragments (#6626)

* Apply suggestions from code review
Apply to cloud-serverless

Co-authored-by: Scott Anderson <[email protected]>

* fix(influxdb3): broken links and aliases:

The link in the cloud-serverless schema-design page was pointing to /influxdb3/cloud-serverless/reference/line-protocol/#duplicate-points, but the actual file is located at /influxdb3/cloud-serverless/reference/syntax/line-protocol/
Core/Ent3 aliases were missing trailing slash, preventing navigating directly from other product line protocol docs

* chore: cleanup

* fix(ci): skip fragment validation for local file URLs in link-checker

Workaround for link-checker Hugo pretty URL bug where /path/to/page#fragment
is converted to file:///path/to/page#fragment instead of
file:///path/to/page/index.html#fragment.

All 60 'broken' fragments reported by CI actually exist in the HTML files.

---------

Co-authored-by: Scott Anderson <[email protected]>

Author: jstirnaman

.ci/link-checker/production.lycherc.toml

@@ -92,6 +92,13 @@ exclude = [
   # TODO: Remove after fixing canonical URL generation or link-checker domain replacement
   "^https://docs\\.influxdata\\.com/",
 
+  # Local file URLs with fragments (workaround for link-checker Hugo pretty URL bug)
+  # link-checker converts /path/to/page#fragment to file:///path/to/page#fragment
+  # but the actual file is at /path/to/page/index.html, causing false fragment errors
+  # TODO: Remove after fixing link-checker to handle Hugo pretty URLs with fragments
+  # See: https://github.com/influxdata/docs-tooling/issues/XXX
+  "^file://.*#",
+
   # Common documentation placeholders
   "YOUR_.*",
   "REPLACE_.*",

content/shared/v3-line-protocol.md

@@ -423,7 +423,7 @@ influxctl database create device_status_history --retention-period 400d
 Then write current status to `device_status_current` and historical data to `device_status_history`.
 {{% /show-in %}}
 
-{{% show-in "cloud-dedicated,clustered" %}}
+{{% show-in "cloud-dedicated,clustered,cloud-serverless" %}}
 ### Performance considerations
 
 #### Row count and query performance