Building interactive demos for examples

### Describe the issue linked to the documentation

This is not an issue but rather a good-to-have feature for documentation and this issue is more of a discussion.

It would be nice to have links to or embedding interactive demos made with Gradio inside documentation. 
I've built two apps that you might see how it looks like:
- Anomaly detection: https://huggingface.co/spaces/scikit-learn/anomaly-detection
- Classification: https://huggingface.co/spaces/scikit-learn/classification

We can have below demo (but more official version 😅) embedded in your documentation.
<img width="1155" alt="Ekran Resmi 2022-11-10 15 11 41" src="https://user-images.githubusercontent.com/53175384/201114005-5fd13d40-990a-412d-abe6-fdd01d0f87d9.png">

The current workflow for users is to download python code or run binder. This reduces amount of work in this workflow too!
If you think embedded demos is a bit overkill what we could do is to create these demos and host them on [Spaces](https://huggingface.co/spaces) and put link to Space instead (like it is with Keras examples or kornia examples, you can see them [here](https://huggingface.co/keras-io) and [here](https://huggingface.co/kornia), they're linked from their tutorials on both [Keras.io/examples](https://keras.io/examples/) and Kornia docs) We will also host the Spaces in better hardware (8 vCPU 32 GiB RAM) to make sure it's always running and all good. ✨ 

You can see how it's implemented in Kornia for rst docs [here](https://raw.githubusercontent.com/kornia/kornia/627ebcaaab1547c362908fc9ad9a68c6316c5993/docs/source/filters.rst). It looks like [this](https://kornia.readthedocs.io/en/latest/filters.html#interactive-demo) inside Kornia docs.

<img width="1353" alt="Ekran Resmi 2022-11-10 15 15 08" src="https://user-images.githubusercontent.com/53175384/201114865-d44b6af5-0b85-44d1-b490-0450d8ea05aa.png">

As for Keras, we just put a redirection link inside docs since their document generation is more layered.  
<img width="1309" alt="Ekran Resmi 2022-11-10 15 09 57" src="https://user-images.githubusercontent.com/53175384/201113694-a4c5b804-dce4-4e72-b23e-bbe449bbc150.png">

We definitely want to reduce the core maintainers' workflow so what would be cool is that we (team at [Gradio](https://gradio.app/) & community)  will be developing the demos and maintaining them through GitHub actions such that they will not break every time there's a breaking change in sklearn (this happens rarely, though 🙂)

Hoping to see how we could collaborate!

COMMENT:
Yes, I think the `scikit-learn` team should explore all possibilities and see what makes the most sense on your side that will satisfy your users and community and make technical sense. From our side happy to support you if there's interest! <3  

> if we're doing it, we should then discuss if we'd like to use stlite or gradio-lite. Streamlit has a much larger user community, is more mature, and its much better documented compared to gradio, and I've heard from many users that working with streamlit seems easier.

Happy to discuss async about this, I want to make sure there is an objective discussion here. Gradio has 3.4M monthly pip installs, a significant, thriving usage base (with big projects such as Auto111, etc), and from 🤗 Hub usage, we've seen significantly organic accelerating usage for it. The fact that the community was able to quite independently build [80 demos](https://huggingface.co/sklearn-docs) in some days also tells something, and we're always happy to take feedback on how to improve our docs in [Gradio's repo](https://github.com/gradio-app/gradio) if you feel anything is lacking for sklearn use cases.

In any case, we <3 Streamlit and Shiny and are collaborating closely with them; I hope one of these options (or other pyodide solutions!) work well for you!

Labels: Documentation, RFC