[Cleanup] Remove custom dependency exclusion handling #44363
Description
Our build contains a good deal of code to deal specifically with the handling of excluded dependencies in POM generation. When transitive dependencies are explicitly disabled via transitive = false on either a dependency of configuration, Gradle translates this to a wildcard exclude on the dependency (or all dependencies when put on a configuration). This behavior seemed to cause issues with some Ivy consumers. It seems the most recent Ivy release now properly supports this scenario. We should confirm this is the case, and if possible, remove this custom handling from our build as it requires us to create a bunch of unnecessary configurations for state tracking which undoubtably come at a performance cost.