Allow Custom Naming for EgressFirewall Resources to Enhance Compatibility with GitOps Tools

Currently, the EgressFirewall resource in OpenShift must be named "default". This naming constraint causes issues when using GitOps tools like ArgoCD and kustomize, especially when name transformations such as prefixes and suffixes are applied. This feature request proposes allowing custom naming for EgressFirewall resources to improve compatibility and flexibility in GitOps workflows.

We need the ability to use our own naming conventions to align with organizational standards and best practices.
Current naming restrictions conflicts with a smooth usage of OpenShift GitOps with kustomize, not allowing for usage of basic name transformations.
A workaround exists but it's time consuming, error prone and tedious. Custom naming will simplify the management of EgressFirewall resources, reducing the risk of conflicts and errors in complex deployments.
Automated pipelines can be more effectively implemented without the need for workarounds to handle the "default" naming constraint.

OpenShift EgressFirewall Component
OpenShift GitOps ArgoCD Integration
Kustomize Integration
Any custom scripts or tools that manage OpenShift resources