fix: Allow local IP addresses during validation of an onboarding service

[pavel-jares-bcm]

Description

When configuration of a service does not provided a IP address value Eureka automatically set one. It is first found non-loopbak IPv4 address. It could happened that this address is from another network interface and therefore cannot be validated (the current implementation just translate local hostname to IP address). This issue could happened in many services, so this PR adds all local addresses as allowed. In case of HA the issue still remaining because one instance of DS couldn't know about the whole list of other LPAR. Anyway this PR improve the situation. The follow up US could rewrite Eureka default translation to respect host name.

Type of change

• fix: Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the style guidelines of this project
• PR title conforms to commit message guideline ## Commit Message Structure Guideline
• I have commented my code, particularly in hard-to-understand areas. In JS I did provide JSDoc
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The java tests in the area I was working on leverage @nested annotations
• Any dependent changes have been merged and published in downstream modules

[pablocarle]

Check sonar issues please

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
90.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud