docs: added documentation for the usage of the dependency-checker too…

[MichaelLangbein]

…l. Only affects demo-maps. Handles issue #19

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/dlr-eoc/ukis-frontend-libraries/blob/master/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• The Project is building and passes all tests without errors

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

The project demo-maps has a route licenses. This route displays a component with a list of all the licenses that are being used in the project. That list is being generated with a CLI tool named license-checker.

Issue Number: 19

What is the new behavior?

The usage of license-checker has been documented extensively. After some discussion, it was decided to not include the tool in the standard-build-process, because that would add another dependency for us to manage. Instead documentation has been provided to help consumers of the frontend-libraries to integrate the tool in their own build-process.

Does this PR introduce a breaking change?

• Yes
• No

Other information

This PR affects only the project demo-maps.