Feat switch rundown api

[alex-Arc]

#2079

unsure what a good naming for the api would be (load or switch or...)
should we make it a nested api, will there be mor actions needed on rundown from the api
should we add a way for the user to see the id in the UI

osc example

/api/rundown/load "abcd"

http example

/api/rundown&load=abcd
/api/rundown/load/abcd

websocket

{"rundown": {"load": "abcd"}}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 6ee40202-732c-4181-9af7-13c0422d4a77

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat-switch-rundown-api

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[manoge2002]

I think you've already done a great job laying the groundwork.
The rundown ID definitely needs to be visible in the UI when it's used. Otherwise, I'd definitely go with exactly what you've done.

[cpvalente]

@alex-Arc , we will need to wait with this until the rundown loading code is done

as for API design:

I believe that receiving a title may be too lose of an API, we should stick to rundown IDs, at least for now
Since this is primarily concerning the companion module, we could create a select element that shows all the rundown by title and give users options to load one

Should wait on #2086