DRAFT: Refactor to move Classpath Jar reports into the API module

[kittylyst]

Some of these classes seem to make more sense in the API module, as we need them in the Standard Agent (which is Java 8).

Can people review, please - I feel like this warrants some discussion.

[jponge]

Funnily the conventional commit check configuration hasn't spotted that the commit message is not in the expected format, it should be something refactor!: move classpath Jar reports into the API module like according to https://www.conventionalcommits.org/en/v1.0.0/#summary

Doing a proper review later this morning.

[jponge]

Thanks @kittylyst

From a client maintenance perspective I don't see any objection for moving these classes from the runtime to the API module.

1. This would trigger a 2.0.0 as it's a breaking change and this project shall adhere to semantic versioning.
2. The commit message must follow conventional commit specs (see my comment above / refactor!: move classpath Jar reports into the API module should be a good start, ! is for a breaking change)
3. I'll let @ehsavoie give his take on the impact on the EAP 7/8 clients, if any.

[jponge]

Approved but do not merge right now