Extraneous exportTo setting when applying custom Istio ServiceEntry CRs

Bug

Description

When applying istio.hardened configurations, the customServiceEntries applied to the velero namespace were not taking effect and had a duplicate exportTo attribute.

Configurations for the velero package should follow the standards used in other packages. See the custom service entry logic from the monitoring package as an example.

Note: This same issue happens in the promtail customServiceEntries template as well.

BigBang Version

What version of BigBang were you running?

2.28.1