Capycli

* CaPyCLI is more resilient when accessing SW360.
* Dependency updates:
* idna 3.6 => 3.7 to fix a security vulnerability
* sw360 1.4.1 -> 1.5.0 to have an improved session handling for all api requests.

* Have an updated granularity list.
* New feature that adds a flag `force error` to `project prerequisites` to exit the application
with an error code in case of a failed prerequisites check.
* The flag `force error` is also available for `project getlicenseinfo` and results in an error
code if a CLI file is missing.

* Update dependencies, especially use sw360, version 1.4.1. to fix a problem in `project update`.

* `getdependencies javascript` can now handle package-lock.json files of version 3.
* `bom findsources` can do source URL discovery using sw360 lookup, perform extensive
GitLab deep search, and adapt search strategy based on diverse programming languages.
* Have type support.

* Be more resilient about missing metadata in CycloneDX SBOMs.
* The `-o` parameter of the command `project GetLicenseInfo` is now optional.
But you still need this output when you want to create a Readme.
* `project createbom` add purls, source and repository url from SW360 if available.
If multiple purls are found, a warning is printed asking user to manually edit SBOM.
* `project createbom` adds SW360 source and binary attachments as external reference to SBOM.
* `project createbom` adds SW360 project name, version and description to SBOM.
* `bom granularity` can now read custom granularity data from local files and remote URLs.
* update dependencies, unfortunately vcrpy does not support urllib3 >= 2 and new vcrpy version
result in unit test issues.

* Have an updated granularity list.
* Re-enable support for Python 3.8 and 3.9.
* A list of frequently asked questions has been added.
* `getdependencies python` now also accepts a Poetry lock file (must be `poetry.lock`) as input.
Development dependencies are automatically excluded.
* [Code of conduct](CODE_OF_CONDUCT.md) added.
* Warnings about multiple purls entries when running `bom map` are now only shown if `-v` has been specified.
* breaking change
* `bom map` will report matches by name, but different version **only** if `-all` has been specified.
The original idea of CaPyCLI was to report as many potential matches as possible and to let the user
decide which match to take by editing the SBOM. But it seems that many users did not read the documentation
and the expectations were different. Therefore the default behavior has been changed.
The original behavior of versions prior to 2.x can be enabled via the `-all` switch.