feat: added flag to disable postgresql deployment for enterprise

[RafaelOAiSquared]

Description

Added flag multiwovenPostgresql.enabled, set true by default; which can be used to disable the deployment of postgresql-related services when using a cloud-based database provider.

When setting the flag to false, the following db-related values need to be set as well:

• multiwovenConfig.dbHost
• multiwovenConfig.dbPassword
• multiwovenConfig.dbPort
• multiwovenConfig.dbUsername

Example helm command:

helm upgrade -i multiwoven . \
  --set multiwovenPostgresql.enabled=false \
  --set multiwovenConfig.dbHost=<host> \
  --set multiwovenConfig.dbPassword=<password> \
  --set multiwovenConfig.dbPort=<port> \
  --set multiwovenConfig.dbUsername=<username>

Related Issue

INFRA-22

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• New Connector (Destination or Source Connector)
• Breaking change (fix or feature that would impact existing functionality)
• Styling change
• Documentation update
• Refactoring
• Chore

How Has This Been Tested?

Using an existing kubernetes cluster, with kubectl and helm configured to connect to your cluster:

1. In a terminal, run:

helm upgrade -i multiwoven

2. Confirm a service named multiwoven-postgresql was created in the cluster.
3. In a terminal, run:

helm upgrade -i multiwoven --set multiwovenPostgresql.enabled=false

4. Confirm a service named multiwoven-postgresql is not available in the cluster.

[linear]

INFRA-22 Use Azure Database for PostgreSQL in helm chart

[subintp]

@RafaelOAiSquared Build is failing due to lint error. Please fix that.