deps: bump com.google.cloud:libraries-bom from 26.22.0 to 26.23.0

[diegomarquezp]

continuation of #2166

It previously produced a broken row in library_list.txt due to a grep that produced more than one result when inspecting a monorepo library's .OwlBot.yaml.
I'm assuming we only want the first occurrence since the broken row comes from policytroubleshooting that also has a certain .../iam/v3 that doesn't look involved with the "main" library

[diegomarquezp]

Running autoconfig generation https://github.com/GoogleCloudPlatform/spring-cloud-gcp/actions/runs/6237902294

[diegomarquezp]

I believe this is caused by the library list being faulty.

The generated list contains:

policytroubleshooter, google/cloud/policytroubleshooter
google/cloud/policytroubleshooter/iam/v1, com.google.cloud:google-cloud-policy-troubleshooter, 1ca7973d74d2d16d610c1d8f252263dc5[423](https://github.com/GoogleCloudPlatform/spring-cloud-gcp/actions/runs/6237902294/job/16932539623#step:10:424)bbfd, java-policy-troubleshooter

2 separate lines, which explains why @mpeddada1 found the log with artifact_id=1ca7973d74d2d16d610c1d8f252263dc5423bbfd and so on in her comment

cc: @suztomo

[diegomarquezp]

We only have one case where we get two or more matches.
If instead of selecting the first occurrence we filter with something like v(.*).*java/gapic-google we may fix the issue for policytroubleshooting but we have other older yamls that don't have this pattern (example)

[mpeddada1]

Thanks @diegomarquezp!

[mpeddada1]

Looks like this code generation update is replacing some v1 classes with v2 which is causing the following error:

Error:  /home/runner/work/spring-cloud-gcp/spring-cloud-gcp/spring-cloud-previews/google-cloud-language-spring-starter/src/test/java/com/google/cloud/language/v1/spring/LanguageAutoConfigurationTests.java:[65,53] error: cannot find symbol
Error:    symbol:   class LanguageServiceSpringAutoConfiguration
Error:    location: class LanguageAutoConfigurationTests
Error:  -> [Help 1]
Error:  

@meltsufin @diegomarquezp for the client libraries, v1 and v2 packages live side by side instead of the newer one replacing the older one. Is this something we want to emulate in the Spring?

[diegomarquezp]

googleapis/google-cloud-java@c713970 introduced language/v2. This causes the generated autoconfigs to generate v2 instead of v1 since the script only takes the latest non-alpha/beta version. The language tests depend on v1

Do we want to generate for every version instead?

edit: I oversaw that @mpeddada1 already pointed this out :)

[diegomarquezp]

Removing syntax test subcase as it is not found in v2

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[mpeddada1]

Thank you!