Add MoQ streaming tutorial to docs

[Karolk99]

Description

This PR adds a "MoQ Streaming" tutorial that shows how you can use the MoQ protocol with Fishjam.
It shows how to:

• Create publisher/subscriber token with RoomManager and Production
• Publish stream using Luke's web SDK
• Subscribe (or entire namespace) to a stream using Luke's web SDK

There are missing links because we don't have a blog post or concept section that this tutorial could reference.

Let me also know whether you think we should add a concept section about the MoQ protocol to our docs or stick to the blog post alone.

Edit
I added an "MoQ Streaming with Fishjam" explanation section.

[linear]

FCE-3167 Add MoQ section to DOC

[Copilot]

Pull request overview

Adds a new Fishjam documentation tutorial for MoQ streaming, introducing a docs path parallel to the existing livestreaming guides and showing how to move from sandbox prototyping to production token management.

Changes:

• Adds a new MoQ Streaming tutorial page under docs/tutorials.
• Documents sandbox-based publisher/subscriber token flows and client-side publish/subscribe examples with the MoQ web packages.
• Adds production examples for generating MoQ tokens with the TypeScript and Python server SDKs, including namespace subscription discovery.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[AHGIJMKLKKZNPJKQR]

suggestion: This could be an admonition like :::info and I would phrase it more like:

If you're new to MoQ, then we recommend getting familiar with its [basic concepts](link to blog)

Apart from that, we should add a short TL;DR section defining publishers, subscribers, relays and namespaces. The admonition could mention this section as a more surface-level walkthrough

[Karolk99]

I added a separate page, "MoQ streaming with Fishjam," that is a walkthrough that explains concepts like publisher, subscribers, and path in detail.

[AHGIJMKLKKZNPJKQR]

suggestion: We could demonstrate usage of the moq player component here below or maybe a react component that wraps this logic

[Karolk99]

Would you like to see both? I mean, rewrite already existing code snippets into components and additionally write an example with the players, or change snippets to ready-to-use players?