Recommended-settings install skips SCSS support — provide a non-interactive path

[UltraBob]

Context

The installer's SCSS stage is interactive-only. Choosing Accept recommended settings at the master gate (or DCQ_NONINTERACTIVE=true) skips the stage entirely, even when .scss/.sass files were detected. On SCSS projects, the recommended path silently leaves stylelint covering only **/*.css.

Downstream effect: anyone coaching an install (docs, AI agents, onboarding guides) has to recommend declining recommended settings and answering every prompt manually, just to get SCSS coverage — which defeats the purpose of the recommended path.

Suggestion

Find a better way to enable SCSS support in the recommended-settings context. Some options, roughly in order of preference:

1. Auto-enable on detection. The installer already detects SCSS files to decide whether to ask the prompt. In recommended mode, apply the recommended answer instead of skipping: write DCQ_STYLELINT_GLOBS=**/*.css **/*.scss into .ddev/config.drupal-code-quality.yaml.
2. Automate the manual follow-ups too. Today even a "Yes" answer leaves manual steps: install stylelint-config-standard-scss, swap it into .stylelintrc.json extends, ddev restart. These are scriptable.
3. Add a DCQ_SCSS_SUPPORT variable so non-interactive installs can opt in/out explicitly, consistent with the other DCQ_* variables.
4. At minimum, surface the gap. The final summary should say "SCSS files detected but SCSS support not configured" rather than staying silent.

Acceptance criteria

• A recommended-settings install on a project containing .scss files ends with stylelint actually linting .scss — or with an explicit, visible statement that it does not.
• The final summary reports SCSS support status either way.