Add CLI parameter parsing to bootstrap script

[christianlupus]

Closes #130

This is just a first approach at making the bootstrap bash function CLI parameter-aware.

Feel free to comment, fix, or reject.

[christianlupus]

Honestly, I did not update the README yet, as I wanted to make sure, the PR is valid and that the CLI can be agreed upon.

[juliusknorr]

Is there a command to catch up the full history manually afterwards? Then we could also list that here.

[christianlupus]

I have found this link. Should I add it in some way (a script?) or just document what would be needed to be done?

[juliusknorr]

A script would of course be nice, but I'd also be fine just documenting it

[christianlupus]

I will have a look into this.

[christianlupus]

I added a small script to unshallow/unpartial any existing repository. This script can be used rather generically.

[juliusknorr]

One small question, otherwise very cool addition 🙏

[juliusknorr]

Gave this some try and works nicely. @christianlupus Could you rebase this to latest master branch? I tried but could not push to your fork.

[christianlupus]

Uups, sorry. Obviously, I missed to set you be able to write to the branch. I will rebase and incorporate soon.

[christianlupus]

OK, I rebased onto master. I think there are no side-effects with other parts of the script. I was unsure about the ordering of the test on the .env file and the CLI parameters. I did not merge, yet, as I wanted to give you a chance to once more look at things. Feel free to merge or comment.

[juliusknorr]

Ordering seems good as we only clone with bootstrap on the initial setup call once I'd say.

[juliusknorr]

Thanks a lot for that.

[juliusknorr]

Might be worth to extend the docs around that a bit as well.