fix: wrong xo config resolved

[JounQin]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)
• If applicable, I’ve added docs and tests

Description of changes

This PR fixes a lot of CI errors which is caused by xojs/xo#741

[JounQin]

rehype-github/packages/break/package.json

Line 37 in 7d7e851

"xo": false,

@wooorm OK, why xo: false is set? That's the root cause of the CI test errors. Please help to confirm the desired behavior so that I can update this PR accordingly.

[wooorm]

Because previously xo used xo: false for nested packages, to continue looking for a parent package.json.
Omitting xo: false, previously, resulted in the defaults being applied.
Which is exactly what xo is now doing when xo: false is used.

[wooorm]

Note: updating this project is complex, you don’t have to do the work, I can do it too!

[JounQin]

Because previously xo used xo: false for nested packages, to continue looking for a parent package.json. Omitting xo: false, previously, resulted in the defaults being applied. Which is exactly what xo is now doing when xo: false is used.

So this seems a new bug which I described at xojs/xo#741 (comment), I'll change the fix then.

[JounQin]

Note: updating this project is complex, you don’t have to do the work, I can do it too!

No worry, I just found bugs and want to fix them, no matter it's in xo or rehype-github, just interesting.

[JounQin]

The only left thing is test-coverage, I think I'll leave it to you and you can fix the test-coverage based on this PR. @wooorm

[JounQin]

It's also fine if you want to close this PR.