fix(template): add CONTROL_PLANE_ENDPOINT_IP to ignoredNodeIPs list in CCM

[tuxtof]

What this PR does / why we need it:

By adding CONTROL_PLANE_ENDPOINT_IP to the ignoredNodeIPs in the CCM config, we ensure
CCM will not assign the CONTROL_PLANE_ENDPOINT_IP as the node IP for any node. This could
previously happen as both CONTROL_PLANE_ENDPOINT_IP and node IP on an external DHCP network
would be learned IPs. In case of a slow DHCP assignment, the CONTROL_PLANE_ENDPOINT_IP
could be assigned as the first learned IP on the VM leading to potential issues when the CCM would then
assign the first IP as the node IP even though it was a floating IP.
It also causing issue with IPAM mode and third-party tools who are using IP from nodes

How Has This Been Tested?:

manual deployment of modified ressources

Release note:

- Set CCM to ignore Control Plane IP

[thunderboltsid]

@tuxtof we're bumping up CCM in #479 already. Can you approve that one, rebase this and keep the scope limited to adding control plane endpoint IP to the ignore IPs list?

[adiantum]

lgtm

[thunderboltsid]

We also need to update the template in test/e2e/data/infrastructure-nutanix/ccm-update.yaml

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 33.00%. Comparing base (0e42e21) to head (8074789).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #480   +/-   ##
=======================================
  Coverage   33.00%   33.00%           
=======================================
  Files          17       17           
  Lines        1809     1809           
=======================================
  Hits          597      597           
  Misses       1192     1192           
  Partials       20       20           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.