The postgres_ann extension has been renamed to alloydb_scann

## Breaking The `postgres_ann` extension has been renamed to `alloydb_scann`. Before you upgrade to [AlloyDB Omni Kubernetes operator](https://cloud.google.com/alloydb/docs/omni/deploy-kubernetes) version 1.1.1, you must drop any indexes created using the earlier `postgres_ann` version, then upgrade AlloyDB Omni, and then create the indexes again using the `alloydb_scann` extension. ## Feature Added a [tutorial](https://cloud.google.com/alloydb/docs/quickstart/integrate-kubernetes) that shows you how to set up a connection from an application running in a Google Kubernetes Engine autopilot cluster to an AlloyDB instance. ## Fix [AlloyDB Omni Kubernetes operator](https://cloud.google.com/alloydb/docs/omni/deploy-kubernetes) version 1.1.1 is now available. This patch fixes the following issues: * Fixed a regression for the AlloyDB Vertex AI integration. * Fixed a bug in which upgrading from version 1.0.0 to version 1.1.0 failed when using injected sidecars. * Fixed a bug in which backups weren't reestablished correctly across failovers when using the Commvault sidecar with high availability (HA) configurations. * Fixed a bug that caused a status to be incorrectly set by the load balancer, resulting in erroneous reports that the database cluster wasn't ready. ## Issue Upgrading to version 1.1.1 of the [AlloyDB Omni Kubernetes operator](https://cloud.google.com/alloydb/docs/omni/deploy-kubernetes) might result in a brief interruption to all database clusters. No data loss is expected.