Support for Resource-type access logs

[jpswing954]

Access logs currently allow for both "Service" and "Resource" type logs, which can be selected from using the CreateAccessLogSubscription API's "serviceNetworkLogType" field:

https://docs.aws.amazon.com/vpc-lattice/latest/APIReference/API_CreateAccessLogSubscription.html

But the current code only allows for passing the request elements "resourceIdentifier", "destinationArn", and "tags":

https://github.com/aws/aws-application-networking-k8s/blob/b0957fc21609d1c1f43cb34ac3e09be6ee18843a/pkg/deploy/lattice/access_log_subscription_manager.go#L54C1-L55C1

When "serviceNetworkLogType" is not specified in an API request, the "Service" type log is assumed, which means there is no way to add "Resource" type logs.

[SinghVikram97]

Hi @jpswing954,

For now the controller only manages Lattice services, not resource configurations. The serviceNetworkLogType field is only relevant when the access log subscription targets a service network (i.e., AccessLogPolicy with targetRef pointing to a Gateway), and controls whether to log
SERVICE traffic (HTTP/gRPC) or RESOURCE traffic (TCP through resource configurations).

That said, a service network can have both services and resource configurations — users who create resource configurations outside the controller (via Terraform, CLI, etc.) may still want to log that traffic through an AccessLogPolicy targeting the Gateway.

We'll look into adding an optional serviceNetworkLogType field to the AccessLogPolicy CRD spec and passing it through to the CreateAccessLogSubscriptionInput when targetRef is a Gateway.