fix(linux): use a CEF build with H.264 and AAC support

[eleboucher]

Description

Fixes #1535

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

AI disclosure:

• Partially AI assisted (clarify which code was AI assisted and briefly explain what it does).
• Fully AI generated (explain what all the generated code does in moderate detail).

[7w1]

I'm not sure we're allowed to do this?

Proprietary codecs have distribution fees:
https://www.via-la.com/licensing-programs/avc-h-264/#license-fees
https://www.via-la.com/licensing-programs/aac/#license-fees
...which is why most builds don't build with them. If we bundled a cef with those enabled I believe we would be in violation.

On windows/macos it seems like this is worked around by delegating to OS players and whatnot, which seems to be what electron does, wry does similarly since it delegates the entire webview to the system. But for CEF on linux I can't find any actual solution, not sure what electron does there or if it works. Actually electron seems to ship two versions, one with and one without proprietary codecs and just has open issues about licensing? So maybe this is fine? I have no idea

Anyway chromiumembedded/cef#3559 seems to imply we would be subject to licensing fees

[eleboucher]

It's only a cef issue not a wry because WebKit have the proprietary stuff (same as electron so I guess it's fine)