chore: refresh Kotlin README badges/version and add governance files

[jamesarich]

Summary

Standard-compliance hygiene fixes, grouped into one PR. No existing workflow files are touched (an open PR is editing those); the only workflow change here is the brand-new dependency-review.yml.

Changes

• kotlin/README.md (§6.3): add a badge row below the tagline (CI status, License GPL-3.0-or-later, Maven Central org.meshtastic:takpacket-sdk-jvm, Dokka API docs); bump the install snippet version 0.7.0 → 0.8.0 (matches VERSION); fix blob/master → blob/main links.
• .github/PULL_REQUEST_TEMPLATE.md (§8.4): add a concise, multi-language PR template (summary / type of change / cross-binding checklist incl. goldens-regenerated and changelog). No DCO — this repo does not sign off.
• .github/renovate.json (§5.6): enable vulnerabilityAlerts (existing keys untouched; still valid JSON).
• .github/workflows/dependency-review.yml (§5.7): new SHA-pinned dependency-review workflow (copied verbatim from meshtastic-sdk).

Verification

• renovate.json parses as valid JSON.
• 0.7.0 no longer appears in kotlin/README.md.
• No workflow file other than the new dependency-review.yml is modified.

[coderabbitai]

Warning

Review limit reached

@jamesarich, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 49 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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e927acdf-977c-4eec-a675-d02a18964cc3

📥 Commits

Reviewing files that changed from the base of the PR and between 9259cfb and 95d2928.

📒 Files selected for processing (4)

• .github/PULL_REQUEST_TEMPLATE.md
• .github/renovate.json
• .github/workflows/dependency-review.yml
• kotlin/README.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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