fix(docs): the API reference documented nothing

[damwilin]

Summary

The docs workflow (.github/workflows/docs.yml) publishes the Dokka API reference under /api, but the reference it produced was empty: an "All modules" page with nothing behind it. Every module's Dokka block suppressed all source sets except one called main, and Dokka's Android adapter never creates one - it names source sets after the variants (debug, release, staging and the test ones). So every source set was suppressed and each module reached the generator with sourceSets=[] ("Nothing to document").

The fix keeps the release source set, suppresses the rest (they all document the same src/main/java, and one set keeps source-link merging unambiguous) and labels it android in the rendered pages. Same task, same output directory, so the workflow and the site layout are unchanged.

Type of Change

• Bug fix
• Feature
• Documentation
• Refactor or cleanup
• CI/build/release
• Breaking change

Affected Areas

• API module
• Player module
• Camera recording/upload module
• Android TV module
• Demo app
• Documentation
• Build or publishing

Testing

• ./gradlew testDebugUnitTest --no-daemon --stacktrace - :player re-run green after the change (build-script only)
• ./gradlew :app:assembleDebug --no-daemon
• Manual playback/upload/recording test
• Not run, reason: no runtime code changed

./gradlew dokkaGeneratePublicationHtml: 1168 HTML pages (api 737, player 365, recording 64), root index lists the three modules with their Module.md blurbs, BunnyStreamApi / BunnyStreamPlayer / BunnyLiveStreamPlayer / StreamCameraUploadView pages present, no org.openapitools pages, zero classpath warnings. Rendered locally with mkdocs + the Dokka output the way the workflow assembles the site.

SDK User Impact

None at runtime. The published API reference goes from empty to complete once the docs workflow runs (it triggers on version tags or manually); GitHub Pages must be enabled on the repository with "GitHub Actions" as the source.

AI Assistance

• No substantial AI assistance was used.
• AI helped with this PR; I reviewed and understand the final changes.

Checklist

• The PR is focused on one clear change.
• Public API or behavior changes are documented.
• Tests or manual verification are included where appropriate.
• No secrets, access keys, or private data are included.