chore(repo): add github hygiene, contributing and code of conduct

[InstaZDLL]

Brings waveflow-android up to the shared WaveFlow repo-hygiene baseline (it was the only repo with no .github/ at all).

Added

• Issue templates — bug_report.yml, feature_request.yml, config.yml (blank issues disabled, links routed to SECURITY + the main WaveFlow discussions), adapted to Android (Android version, device/emulator, logcat, MediaStore tag notes).
• pull_request_template.md — Conventional-Commits reminder + ./gradlew testDebugUnitTest / lintDebug checklist, light/dark theme + media-controls checks.
• SECURITY.md — private disclosure policy, Android scope (MediaStore parsing, scoped storage escape, exported components).
• dependabot.yml — weekly gradle + github-actions ecosystems, grouped, labeled.
• labeler.yml + label-pr.yml — path-based scope:* labels + title-driven type:* + diff-driven size:*, same workflow as desktop/ios.
• CONTRIBUTING.md — links the canonical desktop guide, adds the Gradle/JDK-21 specifics.
• CODE_OF_CONDUCT.md — Contributor Covenant 3.0, same as the other repos.

Not included (by decision)

• No CI / CodeQL workflow — the Gradle build/test pipeline is intentionally left out of this hygiene pass to avoid churn against the build config; it can land in a dedicated PR.

The matching label set (type:/size:/scope:/needs triage/gradle…) was created on the repo separately (out of tree), so labeler.yml and the templates resolve on day one.

No app code touched.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 5 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: d383fc92-95f9-4884-9a72-0ba295af2cbd

📥 Commits

Reviewing files that changed from the base of the PR and between 6b1fc55 and 7cc5bb7.

📒 Files selected for processing (10)

• .github/ISSUE_TEMPLATE/bug_report.yml
• .github/ISSUE_TEMPLATE/config.yml
• .github/ISSUE_TEMPLATE/feature_request.yml
• .github/SECURITY.md
• .github/dependabot.yml
• .github/labeler.yml
• .github/pull_request_template.md
• .github/workflows/label-pr.yml
• CODE_OF_CONDUCT.md
• CONTRIBUTING.md

---

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