Fix: use option.cwd to resolve shared config

[yaodingyd]

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

[ ] Documentation update
[ ] 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
[x] Other, please explain:

Add additional fix to #7328

What changes did you make? (Give an overview)

Add cwd passed from CLIEngine to resolve shared config.

When 7328 was closed, the requested change is partial done: baseConfig.extends is resolved not to __dirname but process.cwd(), however it misses the part it can also be resolved to cwd passed from CLIEngine options. This implementation adds resolve to cwd configured by user.

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

[jsf-clabot]

All committers have signed the CLA.

[not-an-aardvark]

Hi, thanks for the PR. May you please fill out the bug report template or provide a reproducible example where ESLint works incorrectly? From your commit message it seems like this is a bugfix, but I'm not sure I understand the bug that it's attempting to fix.

The logic that you're modifying may be about to significantly change and is quite complicated, so I'm hesitant to make it more complex at this point given that the current behavior has apparently been in place for several years.

[yaodingyd]

@not-an-aardvark The RFC is exactly what I want to achieve. Thank you!