apigee: added SLASH_22 support for peering_cidr_range on google_apigee_instance

[ochorne]

Google updated perring range for eval org provisioning. The value must be 22 for an eval installation. Is it possible add SLASH_22 support for peering_cidr_range on google_apigee_instance. Now i have issue then i try create google_apigee_instance with default range SLASH_23 for Eval org

[edwardmedia]

It appears api has updated the enums. It used to be SLASH_23. Now it is SLASH_22
https://cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations.instances#cidrrange
SLASH_23 is no longer valid

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.