[Squid] update documentation ( LLM Generated )

[qcorporation]

Proposed commit message

This PR updates the Squid integration documentation with improved, AI-generated content that has been manually reviewed and verified against official Squid documentation.

What changed:

New documentation added:

• Add docs/knowledge_base/service_info.md with setup instructions, troubleshooting, and vendor resources
• Fix README vendor setup steps to match official WatchGuard documentation
• Fix Vale linting

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices (N/A - no dashboard changes)

Author's Checklist

• Documentation verified against official Squid documentation
• Vale linting issues resolved
• Setup steps match official Syslog configuration guide
• Licensing information verified (standard syslog is built-in feature)

Related issues

• Update documentation for squid

[github-actions]

Vale Linting Results

Summary: 16 warnings, 2 suggestions found

⚠️ Warnings (16)

File	Line	Rule	Message
packages/squid/_dev/build/docs/README.md	103	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/squid/_dev/build/docs/README.md	114	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/squid/_dev/build/docs/README.md	126	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/squid/docs/README.md	103	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/squid/docs/README.md	114	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/squid/docs/README.md	126	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/squid/docs/README.md	215	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/squid/docs/README.md	228	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/squid/docs/README.md	250	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/squid/docs/README.md	270	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/squid/docs/knowledge_base/service_info.md	75	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/squid/docs/knowledge_base/service_info.md	77	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/squid/docs/knowledge_base/service_info.md	87	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/squid/docs/knowledge_base/service_info.md	89	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/squid/docs/knowledge_base/service_info.md	100	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/squid/docs/knowledge_base/service_info.md	102	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.

💡 Suggestions (2)

File	Line	Rule	Message
packages/squid/_dev/build/docs/README.md	33	Elastic.WordChoice	Consider using 'select, press, visits' instead of 'hit', unless the term is in the UI.
packages/squid/docs/README.md	33	Elastic.WordChoice	Consider using 'select, press, visits' instead of 'hit', unless the term is in the UI.

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: f329164

cc @qcorporation