Change the deployment rhythm

[jacquesfize]

To simplify the development process of version 1.0, we deployed it to the GitHub pages each time we made a commit on the main branch.

Now that a first stable version is available, perhaps it's time to slow down the deployment process to once per release.

[jacquesfize]

As of today, functionalities are still deployed directly after the merge in the main branch. However, automatic testing of BAM is now operational with E2E tests and unit test

[jacquesfize]

in #143, I propose to display both version and commit in the footer.

Another thought, maybe for each new feature we can make a release ?

[camillemonchicourt]

I prefer to group features for releases, but yes we should do some more often.