Default env variable value for schema endpoint

Type of change

• Bug Fix
• Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)

Does this introduce a change in the core logic?

• [NO]

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

• AWS
• Azure
• GCP
• IBM

Does this introduce a breaking change?

• [YES/NO]

What is the current behavior?

Due to lack of default value, pipelines are broken with Storage service not coming up with error

***************************
APPLICATION FAILED TO START
***************************

Description:

Failed to bind properties under 'schema.endpoints.disabled' to boolean:

    Property: schema.endpoints.disabled
    Value: 
    Origin: System Environment Property "schema_endpoints_disabled"
    Reason: failed to convert java.lang.String to boolean

Action:

Update your application's configuration

What is the new/expected behavior?

Default value provided for application property schema.endpoints.disabled

Have you added/updated Unit Tests and Integration Tests?

Any other useful information