#338 Readiness feature implementation

Type of change

• Bug Fix
• Feature

Does this introduce a change in the core logic?

• [Yes] Adds new route /readiness as suggested in #338 (closed), as well as logic to use core services /actuator/health endpoint as reference for springboot services.

Does this introduce a change in the cloud provider implementation, and if so which cloud?

• AWS
• Azure
• GCP
• IBM

Does this introduce a change that must be documented in the README.md file?

• [No] Internal endpoint for readiness check.

Updates description?

Proposed solution for RAFS readiness, to use an optional SERVICE_READINESS_URLS env var to define services that are dependencies of rafs ddms like storage or schema service, see #338 (closed) for reference, put the needed url liveness/readiness services to be checked separated by coma.

In Example:

SERVICE_READINESS_URLS="http://storage/api/storage/v2/liveness_check,http://schema/api/schema-service/v1/liveness_check"

NOTE This is an optional feature, omit setting up SERVICE_READINESS_URLS env var if don't need to use it at all.

@Yan_Sushchynski @kimjiman feel free to push changes for gcp/aws if you plan to use this optional feature or include any devops/infrastructure stakeholders in this MR.

Closes #338 (closed)