Ignore erroneous auto-scale configuration, but warn

[berland]

Issue
Resolves #9339

Approach
Detect and ignore (but warn)

• PR title captures the intent of the changes, and is fitting for release notes.
• Added appropriate release note label
• Commit history is consistent and clean, in line with the contribution guidelines.
• Make sure unit tests pass locally after every commit (git rebase -i main --exec 'pytest tests/ert/unit_tests -n logical -m "not integration_test"')

When applicable

• When there are user facing changes: Updated documentation
• New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
• Large PR: Prepare changes in small commits for more convenient review
• Bug fix: Add regression test for the bug
• Bug fix: Create Backport PR to latest release

[eivindjahren]

Don't think we should change anything in the test-data. Maybe we could instead just edit this in the test.

[eivindjahren]

Currently edits the test-data in place, this should instead just be handled in the test to avoid coupling tests together.