chore: exclude config-docs-generator from workspace

[Jiloc]

Description

Stop building config-docs-generator when running cargo build.

The crate is still being built and used in CI: https://github.com/stacks-network/stacks-core/actions/runs/16906844825/job/47899670930?pr=6371

Applicable issues

• fixes #

Additional info (benefits, drawbacks, caveats)

Checklist

• Test coverage for new or modified code paths
• Changelog is updated
• Required documentation changes (e.g., docs/rpc/openapi.yaml and rpc-endpoints.md for v2 endpoints, event-dispatcher.md for new events)
• New clarity functions have corresponding PR in clarity-benchmarking repo
• New integration test(s) added to bitcoin-tests.yml

[fdefelici]

LGMT!

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.95%. Comparing base (a9e2828) to head (99642fd).
⚠️ Report is 78 commits behind head on develop.

❌ Your project status has failed because the head coverage (75.95%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@             Coverage Diff              @@
##           develop    #6371       +/-   ##
============================================
+ Coverage    62.44%   75.95%   +13.51%     
============================================
  Files          552      549        -3     
  Lines       351797   348635     -3162     
============================================
+ Hits        219676   264816    +45140     
+ Misses      132121    83819    -48302     

see 403 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a9e2828...99642fd. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.