Supply a parameter to create a feature branch instead of pushing towards main and develop branches

[gboder]

The current execution process aims to start from an empty directory where nothing gets overwritten nor edited after its execution. Given this would not be the case or the procedure would be conducted against an already existing repository having the branch protection mechanism already in place pushing the changes applied to the main/ and develop/ branches would fail.

Introduce a parameter letting the user determine whether the changes should apply, as today, to the main/-branch and then used as base to create the develop/-branch or, ignore the existence of those two branches and create a new feature/automed-repo-initialization-feature branch.

The second option is only available given we are working within a pre-existing repository.