TSConfig include parsing throws an error on non-file paths

[JoshuaKGoldberg]

🐛 Bug Report

• TypeStat version: 0.6.2
• TypeScript version: 4.8.4
• Node version: 18.7.0

Actual Behavior

josh ~/repos/typescript-static-analysis-hidden-gems $ npm run typestat:incompleteTypes

> [email protected] typestat:incompleteTypes
> typestat --config ./src/typestat/incompleteTypes/typestat.json

Usage: typestat [options]

Options:
  -c --config [config]    path to a TypeStat config file
  -l --logfile [logfile]  path to a logfile to print detailed logs in
  -V --version            output the package version
  -h, --help              display help for command

Error: ENOTDIR: not a directory, scandir '/Users/josh/repos/typescript-static-analysis-hidden-gems/next-env.d.ts'

This is happening because include is ["next-env.d.ts", "**/*.ts", "**/*.tsx"], and TypeStat is trying to read each of those as a directory:

TypeStat/src/options/parseRawCompilerOptions.ts

Lines 33 to 35 in ba26bf7

	.flatMap((include) =>
	fs.readdirSync(path.join(rootDir, include)).map((fileName) => path.join(rootDir, include, fileName)),
	)

Expected Behavior

TypeStat should use the same mechanisms that TypeScript internally uses to convert TSConfig includes into a list of files.

Reproduction

JoshuaKGoldberg/typescript-static-analysis-hidden-gems@213dd04