IssueTracker

Problem you have encountered:

As the title suggests, following the docs (https://cloud.google.com/identity-platform/docs/admin/email-enumeration-protection), will enable enumeration protection, but only to its default native tenant, and it is not propagated to tenants belonging to the project. Apologies if this is how it is designed, but in that case, I expect a documented method for tenant-specific configurations.

What you expected to happen:
Either of the two:
- REST API to toggle the project configuration to actually propagate its settings to tenants, given that they belong to the same project as well;

- Have a tenant-specific API that we can access so we can configure it in a similar way as the project-wide setting (And have it documented so it is clear what to do).

Steps to reproduce:

1. Create a project
2. Enable Identity Platform
3. Enable multitenancy, create a tenant
4. Create a user under the project directly, as well as inside the tenant
5. enable the Enumeration Protection via the REST API (link)
6. Login with wrong credentials on either account, shows different messages (Project native has enabled protection).

Other information (workarounds you have tried, documentation consulted, etc):