Add support for API interactions used to start and maintain a camera live stream

[DavidValeri]

Introduces the methods mapping to the API interactions for initiating a stream, checking on the stream initiation status, and maintaining the stream in an active state.

Here is a use case in action https://github.com/DavidValeri/bb-streamer. The output can be fed to an NVR or another identification system.

[DavidValeri]

This should probably include an optional timeout on this waiting loop.

[jhansche]

I initially did not go down the path of adding live streaming to the integration, because while the camera is in live streaming mode, it cannot detect bird visitors.

That said, I'm less opposed to adding support for this into the pybirdbuddy library itself (more opposed in the HA integration, because it restricts the primary purpose and intention of the BB).

[Erreon]

Code review

Found 2 issues:

1. watching_start and watching_start_check declare feeder: Feeder but the method bodies handle the case where feeder is a plain string (else: feeder_id = feeder). Every other analogous method in the file uses feeder: Feeder | str (e.g., toggle_off_grid, toggle_audio_enabled, set_power_profile, update_firmware_start). The type annotation should be Feeder | str to match the implementation.

pybirdbuddy/birdbuddy/client.py

Lines 248 to 250 in e5e5031

	async def watching_start(self, feeder: Feeder) -> dict:
	if isinstance(feeder, Feeder):

pybirdbuddy/birdbuddy/client.py

Lines 284 to 286 in e5e5031

	async def watching_start_check(self, feeder: Feeder) -> dict:
	if isinstance(feeder, Feeder):

Compare with the existing pattern:

pybirdbuddy/birdbuddy/client.py

Lines 320 to 323 in e5e5031

	async def toggle_off_grid(
	self,
	feeder: Feeder | str,
	is_off_grid: bool,

2. The variables dict in both watching_start and watching_start_check includes a top-level "feederId" key, but neither the WATCHING_START nor WATCHING_START_CHECK GraphQL mutations declare a $feederId parameter -- they only declare $startWatchingInput: StartWatchingInput!. The extra undeclared variable is inconsistent with every other method in the file, where variables exactly match the mutation signature. Strict GraphQL servers will reject undeclared variables.

pybirdbuddy/birdbuddy/client.py

Lines 257 to 262 in e5e5031

	variables = {
	"feederId": feeder_id,
	"startWatchingInput": {
	"feederId": feeder_id,
	},
	}

Mutation signature showing only $startWatchingInput is declared:

pybirdbuddy/birdbuddy/queries/feeder.py

Lines 3 to 5 in e5e5031

	WATCHING_START = """
	mutation watchingStartV2($startWatchingInput: StartWatchingInput!) {
	watchingStartV2(startWatchingInput: $startWatchingInput) {

🤖 Generated with Claude Code

_{- If this code review was useful, please react with 👍. Otherwise, react with 👎.}