[EKS Auto Mode]: An application network policy with the same name as a network policy will conflict

When a network policy is created with the same name as an existing application network policy (or vice versa), the new resource will not be applied.

This means that the networking does not work correctly for the pod/namespace.

Reproduction:
- Create Application Network Policy
- View `PolicyEndpoints` and see that an endpoint is created for the policy
- Create Network Policy in same namespace with same name
- View `PolicyEndpoints` and see that a new endpoint has not been created

Start by reproducing the sequence in EKS Auto Mode: create an Application Network Policy, inspect its PolicyEndpoints, then create a same-named Network Policy in the namespace. Determine why the second policy does not receive a PolicyEndpoint; done means same-named policies are both applied and networking works correctly for the pod or namespace.

Written by the indexing model from the issue text.