Booking of DSIDs with commit script

Changes introduced

• Two new run stages for the commit script:
  • Dry-run (triggered by --dryrun) which will just simulate where each DSID will be placed and what will be added to git. It will not actually copy dummy DSIDs to their final location, create any git branch or push anything to git
  • No-git run (triggered by -n or --nogit) which will copy dummy DSIDs to their final location and simulate what will be added to git. It will not stage any commit or push anything to the remote. At the end it will print out which command to use in order to upload files to git (see below)
• DSID booking logic: only continuous blocks of DSIDs are used (see tests below)
• Possibility to define custom branch name by using -b=branchName

Tests

Testing correct assignment (passes)

Currently we have the following free DSIDs for Pythia 8: 800025-800027 (3 DSIDs), 800030 (1 DSID), 800037-800040 (4 DSIDs), 800045- (many DSIDs). In order to check if the script works correctly I try to submit 2, 3, 4, 5 new DSIDs:

• 2 new DSIDs: should be assigned to 800025, 800026:
  

• 4 new DSIDs: should be assigned to 800037-800040:

• 5 new DSIDs: should be assigned to 800045-800049:
  

Illustration of printouts when DSIDs are assigned

Issues resolved

Closes #94 (closed)