Fix shadow jar

[littleaj]

The shadowJar was repackaging way more than it should. This fixes it.

Here's the gist:

• By default, shadowJar repackages everything in the runtime configuration
• runtime.extendsFrom compile i.e. runtime inherits all behaviors from compile.
• Since provided was defined so compile inherited its behaviors, this created an unwanted transitive link causing everything defined as provided to be repackaged. Really, we just need these on the classpath (see changes to provided-configuration).

As a result of fixing what is repackaged:

• Classes in :agent are no longer accessible and shouldn't be, hence the changes to java files.
• Apache's poorly named method StringUtils.isEmpty actually does check for null :)

Also,

• There's no reference to the Apache HttpClient in :web; only in its tests. So, that dependency was reclassified.

[dhaval24]

Great work! Thanks Arthur for covering me here

[littleaj]

@dhaval24 Happy to help!

Before merging, I want to make sure the provided configuration is working properly across the board. Do you have a test application using spring to test against?

[dhaval24]

Yes I do have it for testing. The same document db application with AI. However it’s on my local box so I am not sure If I could provide you till Monday as I will be back in office then only.

[dhaval24]

#491 is related issue. @littleaj I believe this PR fixes that too? Correct me if I am wrong.