Enable feature flag 'validation.spatial.longitude.enableExtendedRange' for AWS

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
• Google Cloud
• IBM

Does this introduce a breaking change?

• [NO]

What is the current behavior?

Without this feature, search can't handle the longitude outside the range [-180,180].

What is the new/expected behavior?

With this feature, search handle the longitude outside the range [-180,180].

Have you added/updated Unit Tests and Integration Tests?

Any other useful information

Related MR update os-core-common version in azure module to enable enableExtendedRange flag