Use lalr parser for main ert config

[eivindjahren]

This is for performance reasons. May cause ambiguous config files to no longer be parsed, but it should not have any effect.

• 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

[codspeed-hq]

CodSpeed Performance Report

Merging #9735 will not alter performance

_{Comparing eivindjahren:use_lalr_parser_for_main_ert_config (d7800df) with main (60fc8f8)}

Summary

✅ 24 untouched benchmarks