🧩 Update Config Generation And Validation

[thorstenfoltz]

• 🧪 Keep global settings ahead of provider blocks so generated configs remain easy to scan and compare.
• 🧱 Write out the full supported config surface by default, including updated provider limits and Ollama startup tuning.
• ✅ Strengthen validation and ordering to stay aligned with defaults and preserve provider grouping at the end.
• 🧪 Expand tests to lock in the new config shape and prevent regressions in wizard output and default serialization.

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ PYTHON	bandit	5		0	0	1.78s
✅ PYTHON	black	5		0	0	2.42s
✅ PYTHON	flake8	5		0	0	0.95s
✅ PYTHON	isort	5		0	0	0.3s
✅ PYTHON	mypy	5		0	0	13.44s
✅ PYTHON	pylint	3		0	0	6.64s
✅ PYTHON	pyright	5		0	0	3.45s
✅ PYTHON	ruff	5		0	0	0.02s
✅ REPOSITORY	checkov	yes		no	no	19.2s
✅ REPOSITORY	gitleaks	yes		no	no	1.31s
✅ REPOSITORY	kics	yes		no	no	0.98s
✅ REPOSITORY	ls-lint	yes		no	no	0.29s
✅ REPOSITORY	secretlint	yes		no	no	1.23s
✅ REPOSITORY	semgrep	yes		no	no	35.53s
✅ REPOSITORY	trivy	yes		no	no	11.24s
✅ REPOSITORY	trufflehog	yes		no	no	4.58s

See detailed reports in MegaLinter artifacts
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff