Fix error reporting not shown when running model validation

[AAraKKe]

What does this PR do?

Fix ddev error reporting when validating config files.

Note: this is a stack on the previous PR because I was building a new integration with the worktrees fix to avoid any modification to take to long to validate, lint or format.

Motivation

When running ddev validate config if the schema of the spec is malformed the validation fails but errors are not reported because we skip the update before updating the display_queue. This update would allow us to get information about what failed when parsing the spec file.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[AAraKKe]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Fix error reporting not shown when running model validation #20445 👈 (View in Graphite)
• Ensure that ddev does not treat worktrees as extra packages #20444
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.06%. Comparing base (8a1befa) to head (166494e).

Additional details and impacted files

Flag	Coverage Δ
activemq	?
cassandra	?
confluent_platform	?
datadog_checks_dev	77.61% <ø> (ø)
falco	?
hive	?
hivemq	?
hudi	?
ignite	?
jboss_wildfly	?
kafka	?
kuma	?
litellm	?
mac_audit_logs	?
presto	?
solr	?
tomcat	?
weblogic	?

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.