Update koop to latest monorepo version

Type of change

• Bug Fix
• Feature
• Dependency Upgrade
• Documentation

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

Does this introduce a change in the core logic?

• [YES/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]
• Provider service which previously required the "/gcz/" in the URL path will no longer be compatible
• How to upgrade? - Please update URLs to not include "/gcz/"
  • You may also download our updated Postman Collection which features the updated endpoints
  • 

What is the current behavior?

• Using outdated Koop version
• Arbitrary :id (gcz) parameter required in the Request path for Provider URLs (ignite-provider/rest/services/gcz/FeatureServer`
• Hitting /FeatureServer endpoint without specifying layer ID resulted in error instead of an ArcGIS compatible service definition
• Default Application.yml values pointing toward decommissioned M19 RI endpoints

What is the new/expected behavior?

• Updates Koop to latest version (performance & security updates)
• Removes gcz from Service endpoint so new endpoint is: ignite-provider/rest/services/FeatureServer/:layer
• Now requests to FeatureServer endpoint without layerID will respond with general service definition
• Application.yml values now point to M20 RI endpoints.

Have you added/updated Unit Tests and Integration Tests?

• Postman Collection updated

Any other useful information

• Post_Deployment Test Docs updated to use full "ignite-provider/rest/services/FeatureServer" endpoint instead of the shorter, defunct "ignite-provider/gcz/FeatureServer" endpoint.