Import split-repo boms into google-cloud-bom

[chingor13]

Rather that specifying all the artifacts from the split repos, we will import the bom artifacts that those repos provide:

• asset
• automl
• core
• datacatalog
• datalabeling
• dlp
• gameservices
• iamcredentials
• iot
• phishingprotection
• speech
• talent
• tasks
• texttospeech
• trace
• translate
• vision
• websecurityscanner

[codecov]

Codecov Report

Merging #6554 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #6554   +/-   ##
=========================================
  Coverage     46.35%   46.35%           
+ Complexity    28018    28002   -16     
=========================================
  Files          2613     2613           
  Lines        288075   288075           
  Branches      33774    33779    +5     
=========================================
  Hits         133528   133528           
  Misses       144308   144308           
  Partials      10239    10239

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 19d77e0...2e2d0f3. Read the comment docs.

[anuraaga]

Hello - as we found in gradle/gradle#11208 this PR changed the behavior of google-cloud-bom significantly. It used to be the one BOM to manage them all but now if a user wanted to use, e.g., trace, they have to add an unversioned dependency on the trace-bom too. Just want to confirm, is this the expected new behavior? I can't find any issue to provide more reasoning on the reason to use imported BOMs - if it's to reduce copy-paste, it's probably better for releasetool to inline BOMs instead of importing them to make it easier for users to use the super-bom.

[elharo]

I'm looking into this. I am not certain that Maven behavior is as gradle/gradle#11208 thinks it is.

[elharo]

Update: the comments on the gradle bug are incorrect. For Maven there is no behavior change from 0.116.0 to 0.117.0. Gradle I'm not as familiar with.

[jjohannes]

This is working in Gradle as well. The confusion was created because grpc-google-cloud-trace-v2 is not listed in google-cloud-trace-bom-0.109.0-beta.pom. And because the individual entry was removed in this PR, there is no entry for grpc-google-cloud-trace-v2 anymore (only for grpc-google-cloud-trace-v1).

[anuraaga]

Thanks a lot for investigating this - sorry for not confirming the contents of google-cloud-trace-bom first. Looks like it will be a relatively simple fix to just add to that bom :)