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:
Thanks for the initiative @merveenoyan! I do agree that interactive examples are very effective in generating intuitions and understanding. I think linking to the demos is doable as long as we make it clear to the reader that they are noteworthy but are not maintained by the project itself, as mentioned by @betatim. This should probably include a disclaimer about the privacy/regulatory implications.

Regarding @ogrisel's comment:
> The scikit-learn HTML documentation has no dependency on external online services: it can be generated and browsed locally without any internet connection.

I don't fully agree because we do link to Wikipedia and scientific papers, but I guess the spirit of the comment is more inline with the idea that pre-calculated demos would be better in terms of usability and even computational sources. Doing so would then be the responsibility of the external maintainers.

The only concern about adding external links (even with a disclaimer) is that it may set a precedent that people may use opportunistically to demand linking to their blogposts/projects as long as the content is "relevant", instead of actually contributing to the development of the existing content.

In any case, @ogrisel's solution has my +1:
> If maintainers do not want to have to deal with a doc dependency on remotely maintained code demos on huggingface spaces, then at least it would be worth publishing a blog post with those demos included on [blog.scikit-learn.org](https://blog.scikit-learn.org/) (via [scikit-learn/blog](https://github.com/scikit-learn/blog)).

For the moment I encourage other users, contributors and maintainers to give their opinion!

Labels: Documentation, RFC