Stop publishing tsconfig.tsbuildinfo

[ExplodingCabbage]

This file:

• accounts for roughly two thirds of cliui's package size (both packed and unpacked)
• creates a false/irrelevant mismatch if someone security-conscious naively tries to verify that building cliui from source produces the same output as is published on npm (since building in a fresh clone of the repo will not generate an identical tsconfig.tsbuildinfo to the published one)
• has no reason at all to be published as far as I understand it; per https://www.typescriptlang.org/tsconfig/#tsBuildInfoFile I understand it to be for incremental builds, and https://www.reddit.com/r/typescript/comments/14ejrlk/should_i_publish_the_tsconfigtsbuildinfo/ says not to publish it.

[shadowspawn]

Some background research: gts added composite in 6.0.0 in PR: google/gts#899

Upgrading gts triggered the unexpected file. Some other yargs projects may be affected too.

Large in the context of this project:

npm notice
npm notice 📦  [email protected]
npm notice Tarball Contents
npm notice 731B LICENSE.txt
npm notice 3.4kB README.md
npm notice 9.7kB build/lib/index.js
npm notice 36.4kB build/tsconfig.tsbuildinfo
npm notice 351B index.mjs
npm notice 1.6kB package.json
npm notice Tarball Details
npm notice name: cliui
npm notice version: 9.0.1
npm notice filename: cliui-9.0.1.tgz
npm notice package size: 17.1 kB
npm notice unpacked size: 52.1 kB
npm notice shasum: 24abc6231d4ab72c331c32570c33f31b8a7adba0
npm notice integrity: sha512-pUeDbRPiQ4oQI[...]5qzRe5RMSy2jw==
npm notice total files: 6
npm notice
cliui-9.0.1.tgz

[shadowspawn]

The other yargs packages are using gts v5 so not currently affected.

[shadowspawn]

Other options would be whitelisting published files, or redirecting output to a different folder using tsBuildInfoFile.

However, just blocking *.tsbuildinfo is easy and light.

[shadowspawn]

LGTM