ci: add settings/config.py to core in suitespec

[emmettbutler]

This change fixes an overlooked file inclusion in the suitespec discovered via #7060.

Checklist

• Change(s) are motivated and described in the PR description.
• Testing strategy is described if automated tests are not included in the PR.
• Risk is outlined (performance impact, potential for breakage, maintainability, etc).
• Change is maintainable (easy to change, telemetry, documentation).
• Library release note guidelines are followed. If no release note is required, add label changelog/no-changelog.
• Documentation is included (in-code, generated user docs, public corp docs).
• Backport labels are set (if applicable)

Reviewer Checklist

• Title is accurate.
• No unnecessary changes are introduced.
• Description motivates each change.
• Avoids breaking API changes unless absolutely necessary.
• Testing strategy adequately addresses listed risk(s).
• Change is maintainable (easy to change, telemetry, documentation).
• Release note makes sense to a user of the library.
• Reviewer has explicitly acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment.
• Backport labels are set in a manner that is consistent with the release branch maintenance policy
• If this PR touches code that signs or publishes builds or packages, or handles credentials of any kind, I've requested a review from @DataDog/security-design-and-guidance.
• This PR doesn't touch any of that.

[pr-commenter]

Benchmarks

Benchmark execution time: 2023-09-29 16:30:02

Comparing candidate commit 935a70b in PR branch emmett.butler/internal-settings with baseline commit c26e86c in branch 2.x.

Found 1 performance improvements and 0 performance regressions! Performance is the same for 89 metrics, 0 unstable metrics.

scenario:flasksimple-tracer

• 🟩 execution_time [-318.811µs; -296.284µs] or [-5.068%; -4.710%]