docs: Deploy documentation artifacts to S3

[thomass-dev]

• Replace the use of gh-pages by S3 bucket: the commits history remains light and clean,
• Create a new version of the documentation after each release of skore,
• Add a drop-down list allowing user to select the last 10 versions (+ dev) of the documentation of skore,
• Running locally make html build documentation with a dev tag.

---

After each commit on the main branch, the documentation is build and deployed on the S3:dev/ directory.
After each release, the documentation is build and deployed to the S3:version/ directory, the version being
a subpart of the tag MAJOR.MINOR.BUGFIX: MAJOR.MINOR.

For instance, with the following timeline:

       dev/ dev/ dev/ dev/ dev/                                                                                  
       0.1/                0.2/                                                                                  
main -- x -- x -- x -- x -- x -- >                                                                               
        |                   |                                                                                    
tag    0.1                 0.2       

The S3 bucket looks like:

    .                                                                                                            
    ├── 0.1/                                                                                                     
    ├── 0.2/                                                                                                     
    ├── dev/                                                                                                     
    ├── index.html                                                                                               
    └── versions.json

[rouk1]

Shall we add a stable folder with the latest version of the documentation (a copy) ?
This could allow us to add a canonical link in our heads sections.

<link rel="canonical" href="https://skore.probabl.ai/stable/" />

I think this is better SEO wise especially as shpinx switcher use permanent redirection (301).

For reference Skrub does that.

[thomass-dev]

@rouk1 @jerome-probabl i propose to merge this version in state and refactor in a futur iteration with your comments about

• leaving the python code in a python file,
• making a canonical link instead of a redirection.

[rouk1]

ma-gni-fique 😻