fix: resource concurrency issue and remove sensible information from error messages

Type of change

• Bug Fix
• Feature
• Pipeline
• Test
• Documentation

Does this introduce a change in the core logic?

• No
• Yes

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

• AWS
• Anthos
• Azure
• GCP
• IBM

Does this follow conventional commits spec?

• No
• Yes

Have you set the target Milestone?

• No
• Yes

Have you set the no-detached-pipeline label?

• No
• Yes

Updates description?

To avoid concurrent updates for the database, concurrent dictionary is used which automatically uses mutex to update database.

Method to initialize cosmos client is changed which returns the client if present else creates a new client, also the same client is used to get database and secrets are not exposed anymore.