chore: add iam logging

[JoeWang1127]

In this PR:

• Add logging module in google/iam/v1.
• Regenerate iam.

[sonarcloud]

Quality Gate failed for 'gapic-generator-java-root'

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)
45.5% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud

[sonarcloud]

Quality Gate passed for 'java_showcase_integration_tests'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[lqiu96]

Do you need to add in iam/logging to the proto_path for generation_config.yaml?

sdk-platform-java/generation_config.yaml

Lines 40 to 43 in f587541

	GAPICs:
	- proto_path: google/iam/v1
	- proto_path: google/iam/v2
	- proto_path: google/iam/v2beta

Or is that only for protos with services/ GAPICs. Not too familiar with hermetic build, going to default to Blake's review.

[JoeWang1127]

Do you need to add in iam/logging to the proto_path for generation_config.yaml?

sdk-platform-java/generation_config.yaml

Lines 40 to 43 in f587541

	GAPICs:
	- proto_path: google/iam/v1
	- proto_path: google/iam/v2
	- proto_path: google/iam/v2beta

Or is that only for protos with services/ GAPICs. Not too familiar with hermetic build, going to default to Blake's review.

No need to add a proto_path because logging is a nested directory in google/iam/v1 and all protos inside the proto_path should be generated by default.

I removed the special case in generate_library.sh so that this falls to the default case.

[blakeli0]

Do we know why the transport changed? Is it because this PR #2890?

[JoeWang1127]

Yes, now iam/v2 is used to get the transport.