feat (google STT): support profanity filter

[tinalenguyen]

it was entertaining testing this PR.

docs

Summary by CodeRabbit

• New Features

  • Added a profanity filter option to Google Speech-to-Text, allowing automatic profanity filtering to be enabled or disabled for transcriptions.
  • Profanity filter setting now applies across initial recognition and live streaming transcriptions and can be updated at runtime.

• Documentation

  • Updated parameter documentation and usage notes to include the new profanity filter configuration.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Added a boolean profanity_filter option to the Google STT plugin and propagated it through constructor parameters, option-update methods, and recognition/streaming configuration builders for both Google Cloud Speech v1 and v2.

Changes

Cohort / File(s)	Summary
Google STT core livekit-plugins/livekit-plugins-google/livekit/plugins/google/stt.py	Added profanity_filter: bool to STTOptions; added profanity_filter parameter to STT.__init__; added profanity_filter: NotGivenOr[bool] to STT.update_options and SpeechStream.update_options. Propagated profanity_filter into _build_recognition_config and _build_streaming_config for both cloud_speech_v2 and cloud_speech_v1 paths and into request builders and option-application flows.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐇 I hop through code with careful paws,
A tiny flag to hush the jaws,
From init to stream it softly flies,
Quieting words beneath the skies,
A gentle filter — calm applause.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 20.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding profanity filter support to Google STT, matching the code modifications that add this feature throughout the module.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 56334a9 and ca9b230.

📒 Files selected for processing (1)

• livekit-plugins/livekit-plugins-google/livekit/plugins/google/stt.py

🚧 Files skipped from review as they are similar to previous changes (1)

• livekit-plugins/livekit-plugins-google/livekit/plugins/google/stt.py

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: type-check (3.9)
• GitHub Check: type-check (3.13)
• GitHub Check: livekit-plugins-cartesia
• GitHub Check: livekit-plugins-deepgram
• GitHub Check: unit-tests

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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

[rimiakter5612-arch]

U