Generalize different scraping configurations in a unique branch

[LorenzoLaCorte]

Now, we have several branches for several configurations.

• make constant.py file parametric,
• run one action per configuration, creating different tables
• update the main repository to scrape directly from the several tables

also:

• remove the backups

[LorenzoLaCorte]

Implemented but:

• if the two actions run simultaneously, they both work on the same branch update-results. It can possibly be okay, as far as the second one merges the change of the first one -> just add git merge origin/update-results ?