fix: add --force-conflicts to helm deploy to resolve server-side apply ownership conflicts (#1667)

Helm 4 uses server-side apply which fails when fields were previously
modified by kubectl-edit. Adding --force-conflicts allows Helm to take
ownership of conflicting fields.

Author: zanejohnson-azure

.pipelines/helm-deploy-templates/ama-logs-helm-deploy.yaml

@@ -121,7 +121,7 @@ jobs:
             ${{ else }}:
               overrideValues: 'global.commonGlobals.CloudEnvironment=${{ parameters.cloudEnvironment }},global.commonGlobals.Region=${{ parameters.region }},global.commonGlobals.Versions.Kubernetes=$(K8S_VERSION),OmsAgent.aksResourceID=$(AKS_RESOURCE_ID),OmsAgent.workspaceID=${{ parameters.workspaceId }},OmsAgent.imageRepository=${{ parameters.imageRepository }},OmsAgent.imageTagLinux=${{ parameters.amalogsLinuxImage }},OmsAgent.imageTagWindows=${{ parameters.amalogsWindowsImage }}'
             waitForExecution: false
-            arguments: '--timeout 10m --install'
+            arguments: '--timeout 10m --install --force-conflicts'
         - task: AzureCLI@2
           displayName: Verify Deployment
           inputs: