feat: Support using LoadBalancer service hostname as proxy address

[clement0010]

Changes

• Use LoadBalancer service hostname as proxy address if ip is not available

Notes

Some Cloud providers' (E.g. AWS) LoadBalancer service does not have the ip field in the status.loadBalancer.ingress[0] object.

[Copilot]

Pull Request Overview

This PR enhances service handling by supporting the use of a LoadBalancer service hostname as a fallback when an IP address is unavailable.

• Introduces a new function, get_load_balancer_external_ip, that returns either the IP or the hostname from the ingress.
• Updates test cases to verify the behavior for both IP and hostname scenarios.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
app/handlers/tests/test_handlers_services.py	Updates tests to support both IP and hostname scenarios for LoadBalancer services.
app/handlers/handlers_services.py	Refactors the load balancer validation and retrieval logic to support hostname fallback.

Comments suppressed due to low confidence (1)

app/handlers/handlers_services.py:83

• The error message raised below still refers to 'LoadBalancer IP is not ready', which might be misleading since a hostname is also acceptable. Consider updating the error message to reflect that a valid LoadBalancer external address (IP or hostname) is required.

if not ip and not hostname:

[coveralls]

Pull Request Test Coverage Report for Build 15703856838

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 5 of 5 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.002%) to 96.533%

---

Totals
Change from base Build 15640618433:	-0.002%
Covered Lines:	1221
Relevant Lines:	1247

---

💛 - Coveralls

[minhtule]

Fix & merge!