Auto-disable schema detection for files handled by specific extensions

[shin19991207]

What does this PR do?

Automatically manage common yaml.disableSchemaDetection file patterns when another enabled extension provides more specific YAML support.

Currently handled extensions:

• Docker DX for Docker Compose files
  • Since Docker DX automatically disables its compose language server when vscode-yaml is installed (see https://github.com/docker/vscode-extension/blob/6cc1a9a7acbdd429dc4a085efe2002a21b9cb9ad/src/extension.ts#L146-L157), vscode-yaml only disables schema detection for Docker Compose files when Docker DX is installed and docker.extension.enableComposeLanguageServer is explicitly/effectively set to true.
• GitHub Actions for workflow files
• Azure Pipelines for azure-pipelines.yml and azure-pipelines.yaml

When updating yaml.disableSchemaDetection, vscode-yaml preserves existing user-configured patterns and only adds or removes patterns managed by this feature. If a workspace-level yaml.disableSchemaDetection value exists, the managed patterns are written to the workspace setting. Otherwise, they are written to the global setting.

What issues does this PR fix or reference?

Fixes #1251

Is it tested? How?

• Tested manually

[datho7561]

Looks good and works well from my testing. Thanks, Morgan!

[thernstig]

Since Docker DX automatically disables its compose language server when vscode-yaml is installed (see https://github.com/docker/vscode-extension/blob/6cc1a9a7acbdd429dc4a085efe2002a21b9cb9ad/src/extension.ts#L146-L157), vscode-yaml only disables schema detection for Docker Compose files when Docker DX is installed and

@shin19991207 would it not make sense to remove create an issue for this on Docker DX to fix that so that the extra setting of docker.extension.enableComposeLanguageServer: true does not need to be set by users?