Fix: init error in extending recommended config (fixes #12707)

[yeonjuan]

What is the purpose of this pull request? (put an "X" next to item)

[ ] Documentation update
[x ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

Fix #12707. It still has a triage label but I can reproduce it
reproduced - https://github.com/yeonjuan/autoconfbug

Is there anything you'd like reviewers to focus on?

The cause of the problem is precisely what here mentioned.

RECOMMENDED_CONFIG_NAME is a string, after extendFromRecommended return, the parent scope expect config.extends is an array

[kaicataldo]

Thanks for working on this! Can we test this somehow?

[kaicataldo]

Thanks for adding tests for this! I just had a thought - would it make more sense to put eslint:recommended at the beginning of the array? I can't think of a case where it would be overriding other extended plugins, but can think of cases where the opposite might be true.

Also, would it be possible to write an integration test or two for lib/config-initializer to assert that this works correctly?

[yeonjuan]

@kaicataldo

While I write an integration test code,
I realize that eslint --init doesn't ask for installing modules when I answered with "Inspect your JavaScript file(s)"(answers.source = auto)

So, It ends up with showing error messages below.

Error: Failed to load parser '@typescript-eslint/parser' declared in 'BaseConfig': Cannot find module '@typescript-eslint/parser'

Is it intended?

[kaicataldo]

Sorry I missed this! That seems like a bug to me. Can you make a separate issue for that?

[kaicataldo]

Thanks for contributing!

[yeonjuan]

That seems like a bug to me. Can you make a separate issue for that?
@kaicataldo Sure!