feat: add managed Emby library publishing

[Serph91P]

Summary

• add managed Emby library mappings and a Filament control plane
• publish deterministic versioned catalogs through authenticated Xtream actions
• create and reconcile Emby libraries while excluding managed output from imports
• require explicit PlaylistAuth opt-in and redact companion sync failures

Verification

• focused publishing regression suite: 117 tests, 470 assertions
• vendor/bin/pint --dirty --format agent
• git diff --check
• changed-text ASCII punctuation scan
• npm build, dependency audits, migration checks, and Docker image build completed before delivery

Notes

• app/Services/TmdbService.php and tests/Feature/TmdbServiceTest.php are untouched
• PR intentionally remains Draft

[Serph91P]

Hi @sparkison, this PR is ready for maintainer review. It adds managed Emby library publishing and includes the fail-closed remediation for the delayed Emby library-listing case. The current head has passing focused tests plus green Code Quality, Security Scan, Tests, and Docker Build Validation checks. Please take a look when you have time.

[Grimothy]

looking forward to seeing this. Excellent work this weekend brother

[sparkison]

Noticed a lot of Dispatcharr callouts still (thinking those should be m3u editor now?) in the plugin: https://github.com/Serph91P/m3u-editor-for-emby

also missing the manifests, e.g. https://github.com/Serph91P/m3u-editor-for-emby#installation

thinking we'll want the Emby plugin tightened up a bit before merging this. We'll probably also want a callout somewhere that the plugin is required for this functionality (a callout section with a link maybe?)

[Serph91P]

Noticed a lot of Dispatcharr callouts still (thinking those should be m3u editor now?) in the plugin: https://github.com/Serph91P/m3u-editor-for-emby

also missing the manifests, e.g. https://github.com/Serph91P/m3u-editor-for-emby#installation

thinking we'll want the Emby plugin tightened up a bit before merging this. We'll probably also want a callout somewhere that the plugin is required for this functionality (a callout section with a link maybe?)

@sparkison I didn't merge so the main branch of the plugin does not break until this is merged 😉

That's why I send you the develop branch:
https://github.com/Serph91P/m3u-editor-for-emby/tree/develop
Where it's gone.

The dispatcher call outs are optional for those using dipatcharr but can remove them if you want. M3u editor is automatically detected and you don't even need to choose it.
I can make that more clear in the readme and tooltips and whatnot if you want?

[sparkison]

That's why I send you the develop branch:
https://github.com/Serph91P/m3u-editor-for-emby/tree/develop
Where it's gone.

sorry about that! I'll take another look 👀

[sparkison]

...forget that last commit, meant to push to dev 🙄