chore(license-book): update license book for 7.21.0

[tasso94]

related to #3830

[yanavasileva]

👍 Looks good.

❓ When do we add the source URL for the frontend libraries? Are they required for the end version of the license book? Some of them doesn't have or are incorrect here. E.g.: @bpmn-io/[email protected]

[tasso94]

What do you mean by source URL?
Do you mean repository URL? In case the maintainer of the library didn't add a repository URL to the package.json we cannot determine the repository URL automatically.

[yanavasileva]

👍 Looks good. I noticed some special characters are not resolved correctly, but already approaving as I don't think that a problem with the final version of the book.

[yanavasileva]

🙃 improvements, the below character "issues" are present in the 7.20 book too:

• on row 67, there is some unrecognized characters - https://github.com/camunda/camunda-bpm-platform/blob/3830-update-7.21.0-license-book/distro/license-book/src/main/resources/license-book.txt#L67

(right is CI artifact, left is current file)

• on rows 714-717 special characters are not resolved - https://github.com/camunda/camunda-bpm-platform/blob/3830-update-7.21.0-license-book/distro/license-book/src/main/resources/license-book.txt#L714-L717
  
  (right is CI artifact, left is current file)
• same as above - https://github.com/camunda/camunda-bpm-platform/blob/3830-update-7.21.0-license-book/distro/license-book/src/main/resources/license-book.txt#L734-L743
  
  (right is CI artifact, left is current file)

[tasso94]

I don't know how to fix it. If I use the file directly from the CI, I see other character issues:

The problem might be that notice files were generated for different character sets, and either one or the other characters are broken depending on the current charset.
Since this is already broken with the last license book and the problems are minimal, I would tolerate them. Also, the characters on the left don't look 100 % correct. What's that =>