fix: check for null entries in eureka properties

[pablocarle]

Description

If a service does not define certain eureka properties such as health check relative paths, the respective property ends up being a malformed URL. This PR is a proposal for this sort of scenario.

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

[arxioly]

I understood that we don't want a breaking change, but shouldn't we fix later the problem with "null" in secureHealthCheckUrl?

[pablocarle]

I understood that we don't want a breaking change, but shouldn't we fix later the problem with "null" in secureHealthCheckUrl?

This is a standard eureka field, we could provide a simple default during onboarding also

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud