Refactor ingress status IP address

[aledbf]

What this PR does / why we need it:

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged):

fixes #4461
replaces #4462

Special notes for your reviewer:

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aledbf

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [aledbf]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[aledbf]

/retest

[codecov-io]

Codecov Report

Merging #4490 into master will increase coverage by 0.07%.
The diff coverage is 92.59%.

@@            Coverage Diff             @@
##           master    #4490      +/-   ##
==========================================
+ Coverage   59.03%   59.11%   +0.07%     
==========================================
  Files          89       89              
  Lines        6748     6756       +8     
==========================================
+ Hits         3984     3994      +10     
  Misses       2335     2335              
+ Partials      429      427       -2

Impacted Files	Coverage Δ
internal/ingress/status/status.go	71.97% <92.59%> (+3.51%)	⬆️
internal/watch/file_watcher.go	80.76% <0%> (-3.85%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7d6ce57...62723b9. Read the comment docs.

[harmjanblok]

Not only services of Type LoadBalancer might have externalIPs, services of Type ClusterIP can have this as well. See https://kubernetes.io/docs/concepts/services-networking/service/#external-ips. I'll see if I can create a PR to address this issue.