Update google-apis-admin_directory_v1 requirement from ~> 0.46.0 to >= 0.46, < 0.54

[dependabot[bot]]

Updates the requirements on google-apis-admin_directory_v1 to permit the latest version.

Changelog

Sourced from google-apis-admin_directory_v1's changelog.

v0.53.0 (2024-03-10)

• Regenerated from discovery document revision 20240304

v0.52.0 (2024-03-03)

• Regenerated from discovery document revision 20240227
• Regenerated using generator version 0.14.0

v0.51.0 (2024-02-23)

• Regenerated from discovery document revision 20240220
• Regenerated using generator version 0.13.1

v0.50.0 (2024-01-22)

• Regenerated using generator version 0.13.0

v0.49.0 (2024-01-07)

• Regenerated from discovery document revision 20240102

v0.48.0 (2023-12-24)

• Regenerated from discovery document revision 20231219

v0.47.0 (2023-11-19)

• Regenerated from discovery document revision 20231113

v0.46.0 (2023-10-15)

• Regenerated from discovery document revision 20231005

v0.45.0 (2023-08-27)

• Regenerated from discovery document revision 20230822

v0.44.0 (2023-08-03)

• Regenerated from discovery document revision 20230724

v0.43.0 (2023-05-21)

• Regenerated from discovery document revision 20230516

v0.42.0 (2023-04-30)

• Regenerated from discovery document revision 20230425

... (truncated)

Commits

• ff33830 chore: Update some language prior to releasing separated clients
• dffa55c feat: Automated regeneration of admin directory_v1 client (#2223)
• 26a7770 chore: Move synth.metadata files to new locations
• be13e0c chore: Set yardoc titles (#2144)
• 1e2aeae chore: Update generator to set client version for headers (#2141)
• 388cc7b chore: Initial generation of separate libraries (#2139)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[chef-expeditor[bot]]

Hello dependabot[bot]! Thanks for the pull request!

Here is what will happen next:

1. Your PR will be reviewed by the maintainers.
2. Possible Outcomes a. If everything looks good, one of them will approve it, and your PR will be merged. b. The maintainer may request follow-on work (e.g. code fix, linting, etc). We would encourage you to address this work in 2-3 business days to keep the conversation going and to get your contribution in sooner. c. Cases exist where a PR is neither aligned to Chef InSpec's product roadmap, or something the team can own or maintain long-term. In these cases, the maintainer will provide justification and close out the PR.

Thank you for contributing!

[dependabot[bot]]

Superseded by #778.