Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>

By default the connector will continue to use a refresh ahead strategy,
where client certificates are refreshed by a background thread. The
lazy strategy by comparison is useful for when the Connector runs in
serverless environments and background threads may not run reliably,
e.g., when the CPU is throttled.

This commit adds the lazy refresh strategy and updates the configuration
documentation to demonstrate how to use the feature.

Fixes #565

Bumps [jinja2](https://github.com/pallets/jinja) from 3.1.4 to 3.1.5.
- [Release notes](https://github.com/pallets/jinja/releases)
- [Changelog](https://github.com/pallets/jinja/blob/main/CHANGES.rst)
- [Commits](pallets/jinja@3.1.4...3.1.5)

---
updated-dependencies:
- dependency-name: jinja2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* deps: Update Non-major dependencies

* Remove error prone updates

* Bump error prone annotations

* Update error prone core to latest

* Go back to error prone core 2.31.0 for JDK 11. See https://github.com/google/error-prone/releases/tag/v2.31.0.

---------

Co-authored-by: Eno Compton <enocom@google.com>

JUnit is no longer a problem as we've addressed the underlying
dependency issue in prior changes.

Error Prone core dropped support for JDK 11 in v2.32.0 [1]. So for now,
update Error Prone core separately to make it easier to fix the issue
without breaking our usual dependency updates.

[1]: https://github.com/google/error-prone/releases/tag/v2.31.0

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>