Improved the licenses generated into our shaded jar

[DavyLandman]

This PR introduces the following changes:

• defined our license in the pom.xml file. I had to say only bsd2, as also saying epl1 would be interpreted that our users can pick either license for the whole code)
• the NOTICE file of all shaded dependencies are properly merged
• the LICENSE file of all shaded dependencies are properly merged (future work: it looked like at some point the tutor did that, but that is currently not working)
• a new licenses/ folder is generated with all the downstream licenses, and a xml with a list of all the dependencies and their licenses is stored in the licenses.xml file in the jar.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 49%. Comparing base (c56a6fd) to head (354e452).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##              main   #2016   +/-   ##
=======================================
- Coverage       49%     49%   -1%     
- Complexity    6298    6301    +3     
=======================================
  Files          664     664           
  Lines        59626   59626           
  Branches      8646    8646           
=======================================
- Hits         29476   29472    -4     
- Misses       27939   27942    +3     
- Partials      2211    2212    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jurgenvinju]

This looks great.

• After we have merged typepal and rascal-core we can add the licenses plugin from rascal-language-servers/rascal-lsp and its configuration to this, and make sure all of the rascal project has the right license headers too. missing @license headers in Rascal files (both standard library and test modules) #1342, wrong license headers in many files in rascal project #1344, Replace Eclipse license headers by BSD license headers #1676
• Also the new copied/downloaded files could play a role in the generated website. I'll look into rascal-tutor on where to add that. There is already code for listing the dependencies; seems easy enough to link the downloaded NOTICE and LICENSE files. Copy downloaded LICENSE and NOTICE files of dependencies to the documentation rascal-tutor#37

[DavyLandman]

Thanks!

There is already code for listing the dependencies;

The mvn plugin uses the <license> field of all the pom dependencies, and all our dependencies had it defined (except for vallang, where I've now added it).