[FEATURE] add license option to steps

[mteu]

What changed?

This PR address the feature request from #11 where the GPL license will be selectable and the corresponding legal document will be created upon project creation.

Alternatives?

Instead of listing all potential licenses one might consider outsourcing those files to either sharedFiles or better yet to self-sufficient package. However, in this very case – since we're offering a TYPO3 template – GPL v2/v3 should be most appropriate.

Notice!

In order for this feature being able to be used CPS-IT/project-builder#54 needs to be approved and released. Hence, this PR is kept as a draft until said feature is released.

[eliashaeussler]

Hi @mteu, thanks for your feature proposal.

Generally, actively selecting a license seems like a very good idea to me. However, in context of TYPO3 projects I see two main issues:

1. TYPO3 itself is licensed under GPL 2.0 and requires extensions to be licensed under GPL 2.0 as well (see TYPO3's Open Source Licenses). Even if it's stated that this affects TYPO3 extensions only, I'd highly recommend to also apply these rules to TYPO3 projects as well and to not mix up licenses when working in TYPO3 context.
2. I assume that most TYPO3 projects may never be public, thus being normally developed as a proprietary product. I'd say, additionally defining a license for such cases is a very uncommon way. However, if we decide to include licenses in the template, we should at least provide an option to select a proprietary license.

As a result, I'd vote for not introducing licenses for the TYPO3 project template, as it does not perfectly fit for this use case. When talking about templates for e.g. TYPO3 extensions or generic Composer packages, I'd instantly vote for adding this additional step.

[mteu]

You're perfectly right. Although my understanding of GPL-2.0-or-later differs from yours, let's not overcomplicate things here.