Support for New Ingress/Egress Policy Resources

[sanspace]

TL;DR

Now, Ingress and Egress can be their own resources. It makes it easier to manage and maintain.

Terraform Resources

https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/access_context_manager_service_perimeter_dry_run_ingress_policy
https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/access_context_manager_service_perimeter_ingress_policy
https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/access_context_manager_service_perimeter_dry_run_egress_policy
https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/access_context_manager_service_perimeter_egress_policy

Detailed design

We need to make it easy to add these resources in dry-run mode.

Additional information

I'm interested in contributing to this as I'm working on these new resources

[caetano-colin]

Additional Information:

Currently, if the user adds more ingress/egress policies without using the module, they will be removed from the perimeter, similar to what is described on issue https://github.com/terraform-google-modules/terraform-google-vpc-service-controls/issues/60 for the "resource".

By adding support to the resources above and adding a lifecycle rule, it will allow users to apply additional ingress/egress policies