Decouple stream options from PyAV options

[uvjustin]

Breaking change

create_stream() takes an options dict and passes it straight through to PyAV, which passes it straight into the ffmpeg libraries. This PR adds an intermediate layer through the new STREAM_OPTIONS_SCHEMA and convert_stream_options() function to decouple the options used internally in stream from the options used in ffmpeg. This allows us to 1) restrict the options used to a subset we have tested while also sanitizing them if necessary, 2) change the syntax of the stream options, and potentially 3) group some PyAV options together in a single stream option.
This PR doesn't break anything in core, as the appropriate changes have been made to generic and ONVIF, but this may break some custom components which implement Camera and use the stream_options member to pass in custom PyAV options.

Proposed change

Currently create_stream() takes an options dict which (after having two options added) passes through to the Stream constructor, which in turn passes the options through the stream worker, eventually ending up in the PyAV av.open() function. These options don't seem to be used in the HA code base are used in ONVIF and generic, so those uses were changed here, but it's possible that some custom components also use them.
This PR removes passing the options through directly, decoupling the camera/stream interface from the PyAV API. (Note that currently only one option is supported, and that option is still effectively passed through as is.) If desired, specific options can be defined and checked against in create_stream and then added to the options dict. For example, #71245 can add a boolean option {"rewrite_timestamps" : True} instead of having to know about the PyAV option {"use_wallclock_as_timestamps": "1"}

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[probot-home-assistant]

Hey there @hunterjm, @allenporter, mind taking a look at this pull request as it has been labeled with an integration (stream) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[uvjustin]

stimeout was deprecated/renamed as of ffmpeg 4.0 and will be removed in ffmpeg 5.0:
FFmpeg/FFmpeg@ff46124
FFmpeg/FFmpeg@6f34f03

[davet2001]

Overall looks pretty good to me, just some minor questions.

[allenporter]

Looks great, appreciate this as it will definitely make it more clear how this works for new folks reading the code. 👍🏼

I have a couple minor comments.

[allenporter]

I believe we have a new best practice for changes like this which would be:

• add a short note under "BREAKING_CHANGES" in this PR
• add a short blub in the developer blob e.g. https://github.com/home-assistant/developers.home-assistant/blob/master/blog/2022-04-18-calendar-data-model.md

(I don't think there is widespread use of ffmpeg flags or use of stream in custom components, but just in case it can help.)

[uvjustin]

Marking as draft pending #71245