DRAFT: Add documentation for OpenHound usage and move/replace xHound install instructions

[d3vzer0]

• Adds a new group for OpenHound
• Adds two pages describing how OpenHound is used
  • An enterprise-specific page
  • A community-specifc page
• Adds a global/shared configurations page
• Adds/replaces instructions for OktaHound, GitHound and JamfHound and move them under the /openhound/collectors/* group.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 25da5403-de19-4651-a295-c5753c1dc7e3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[jeff-matthews]

Thank you for the PR @d3vzer0! This is an impressive amount of work ❤️

A couple of things that I think we'll need to address:

1. Fix broken links reported by the mint broken-links command
2. Determine if we should add redirects for the extension-specific files that have moved
3. Update the introduction on the Graph Structure page to contextualize OpenHound (I'm happy to do this one)

Regarding item 2, I don't think redirects are necessary for reference files (there are too many), but maybe just the non-reference pages since those are probably more socialized at this point and are more likely to cause issues.