chore: Complex start up check

[pavel-jares-bcm]

Description

This PR tries to change startup check to wait not only when services are done, but till the moment each service has all services in its own registry.

Not fully related fixes:

• ServerAddressPropertiesUpdater.java‎ - BeanDefinitionRegistryPostProcessor should be static for proper initialization
• ApimlPeerEurekaNode.java‎ - In case on any unknown error we should stop replica, otherwise service (DS/APIML) will be up, but the HA stop working
• EurekaHealthIndicatorApiml.java‎ - fix from chore: Improve start up check #4251: /application/health on apiml provide eureka section with invalid values
• EurekaConfig.java‎ - original Eureka bean is still initializing and causing NPE on shut down (overriding by apimlInstanceRegistry was not fully working)
• RefreshablePeerEurekaNodes.java‎ - DS consider all instancies running on the same host as itself. It didn't take care about ports. Now it is possible to run multiple DS instances on one hostname (like HA)
• ModulithConfig.java‎ - fix Discovery instanceID (use discovery port instead of gateway one)

#4420
#4425

Linked to # (issue)
Part of the # (epic)

Type of change

Please delete options that are not relevant.

• fix: Bug fix (non-breaking change which fixes an issue)
• feat: New feature (non-breaking change which adds functionality)
• docs: Change in a documentation
• refactor: Refactor the code
• chore: Chore, repository cleanup, updates the dependencies.
• BREAKING CHANGE or !: Breaking change (fix or feature that would cause existing functionality to not work as expected)

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

For more details about how should the code look like read the Contributing guideline

[sonarqubecloud]

Quality Gate failed

Failed conditions
69.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud