add IT for shipped/included dependencies vs not-shipped

[hboutemy]

see #589
this PR is not yet about changing anything to generated CycloneDX documents, but listing all cases:

• from the most basic =
  • classical libraries that have transitive dependences = not shipped
  • classical war files = ship dependencies in WEB-INF/lib in .war archive
• to most advanced =
  • shade: very flexible, including partial ship
  • assembly: very flexible configuration file
  • executable archives: ship dependencies, but also adds a launcher (that may even bring a servlet container like Tomcat or Jetty, that is not even listed as a dependency)

see also #576 for a first pass