[Feature Request] Sync the repository tooling under tools/ from upstream Cloud Foundation Fabric #319

Feature Description

Bring tools/tfdoc.py, tools/check_documentation.py and the related test helpers up to the upstream Cloud Foundation Fabric versions, so the README checks work again and regenerated tables match the vendored modules.

Use Case

• The tools/tfdoc.py script predates Fabric v38.0.0 and was never synced, so it renders object types differently from the upstream script that generated the vendored module READMEs.
• Regenerating a synced module README with the local script rewrites every table, so feat(modules)!: sync Cloud Foundation Fabric modules to v59.2.0 and add sync tooling #311 used the v59.2.0 upstream script from a Fabric checkout instead.
• The tools/check_documentation.py check fails on main with an Unknown fixture error, so it cannot guard README tables today.

Proposed Solution

• Three-way merge the tools/ files from Fabric v38.0.0 to the release that modules/ tracks, keeping the Stellar Engine changes such as the Python 3.11 and CodeQL fixes.
• Vendor the tests/fixtures and tests/examples helpers that the scripts import, or make the fixture lookup optional.
• Extend tools/sync-from-cff.sh and tools/cff-sync.ignore to cover the synced tool files, so the weekly sync keeps them current.
• Run tools/check_documentation.py in CI once it passes.

Compliance & Deployment Context

• Target Deployment Type(s):
  • US Region Restricted (e.g., Access Policy constraint)
  • FedRAMP Moderate
  • FedRAMP High
  • DoD IL4
  • DoD IL5
  • All / General
• Relevant NIST 800-53r5 Controls: CM-2 baseline configuration

Reusability Check

Stellar Engine prioritizes reusability.

• I have checked if this functionality can be achieved by extending an existing module or blueprint.
• I have verified that this does not duplicate existing functionality.

Alternatives Considered

• Keep the local script and accept table churn on every sync.
• Run the upstream script from a Fabric checkout, as feat(modules)!: sync Cloud Foundation Fabric modules to v59.2.0 and add sync tooling #311 did, which every maintainer would have to repeat by hand.

Additional Context

• Related: [Feature Request] Sync the modules from upstream Cloud Foundation Fabric and keep them current #308 and feat(modules)!: sync Cloud Foundation Fabric modules to v59.2.0 and add sync tooling #311.