chore: fix documentComponents functions signature

[just-boris]

Issue #, if available:

Description of changes:

It is now 4 arguments, with holes in between, documentComponents(tsconfig, glob, undefined, options). Time to switch from multi-arguments to a single options argument

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.61%. Comparing base (671bd2c) to head (3e86ab1).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #61      +/-   ##
==========================================
+ Coverage   90.55%   90.61%   +0.05%     
==========================================
  Files          16       16              
  Lines         519      522       +3     
  Branches      146      150       +4     
==========================================
+ Hits          470      473       +3     
+ Misses         49       47       -2     
- Partials        0        2       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 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.

[avinashbot]

Won't adding required properties here be backwards incompatible when calling this function from the components package? Unless you're planning on merging a matching components PR at the same time, it would probably be safer to make a new interface for this?

[just-boris]

Downstream packages do not use typescript so the build passes regardless.

And I am planning to migrate to the new signature once it is released and then remove the legacy one here