feat: added iam troubleshooter v3 and v3beta api clients

[alicejli]

New policytroubleshooter client protos are in a different folder than v1. Manually adjusting owlbot file to copy over correctly into the existing module

Tested the Owlbot.yaml file locally and it generates the directories for v3/v3beta correctly:

Command to test locally:

docker run --rm --user $(id -u):$(id -g)   -v $(pwd):/repo -v /tmp/googleapis-gen:/googleapis-gen -w /repo   --env HOME=/tmp   gcr.io/cloud-devrel-public-resources/owlbot-cli:latest copy-code   --source-repo=/googleapis-gen   --config-file=java-policy-troubleshooter/.OwlBot.yaml

[blakeli0]

Tested the Owlbot.yaml file locally and it generates the directories for v3/v3beta correctly:

Did we ever get a library generation requests for v3beta version? If not, maybe just copy the v3 version? WDYT @suztomo?

[alicejli]

Tested the Owlbot.yaml file locally and it generates the directories for v3/v3beta correctly:

Did we ever get a library generation requests for v3beta version? If not, maybe just copy the v3 version? WDYT @suztomo?

We did not get an explicit library generation request for v3beta, but v3beta does exist in the public protos, and in general (I think) our policy has been to generate libraries for whatever exists in the public protos. Can update to whichever is preferred.

[suztomo]

In the ticket that requests library generation, the path to the directory containing proto is explicitly specified up to a version, isn't it?

[alicejli]

In the ticket that requests library generation, the path to the directory containing proto is explicitly specified up to a version, isn't it?

Yes, but for languages like Java we usually automatically update existing modules with new versions as they are published. This library is a bit unique where the new version is published in a different directory than the existing protos, so owlbot didn't catch the new version.

[blakeli0]

We did not get an explicit library generation request for v3beta, but v3beta does exist in the public protos, and in general (I think) our policy has been to generate libraries for whatever exists in the public protos.

I don't think this is true. There is a language section in each library generation request, which sometimes only include a subset of languages, I did see Java being excluded sometimes.