bug: corrupted subdirectory imports

🐛 bug report

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project
  adheres to.
• I have searched the issue tracker for an issue that matches the one I want
  to file, without success.

Description of the problem

GitHub repos with subdirectories that share the same prefix (i.e. examples/with-next alongside examples/with-next-custom-button) will be imported with a corrupted file directory.

Expected file structure:

pages/
styles/

Actual file structure:

pages/
styles/
with-next-custom-button/
with-next-mint-nft/
with-next-siwe-iron-session/
with-next-siwe-next-auth/

How has this issue affected you? What are you trying to accomplish?

This unexpected commingling import behavior will break imported sandboxes and their build system for affected projects. Large projects with monorepo examples/ directories are the most impacted.

To Reproduce

• Attempt to open a Cloud Sandbox for this repo's examples/with-next subdirectory: https://codesandbox.io/p/sandbox/github/rainbow-me/rainbowkit/tree/main/examples/with-next
• Notice that directories including examples/with-next-custom-button will be imported within examples/with-next, even though they exist at the same level as with-next/ in the monorepo's top-level examples/ directory.

Link to sandbox: link (optional)

Reproduce the import from the linked Cloud Sandbox for rainbow-me/rainbowkit at examples/with-next, then compare the expected pages/ and styles/ structure with the actual extra sibling directories. Trace the repository subdirectory selection and import handling until the shared-prefix behavior is located; done means sibling directories such as with-next-custom-button are no longer included.