@mcap/support: remove .d.ts file in favor of module augmentation in source file

[jtbandes]

Changelog

@mcap/support: Fixed a TS error from an import that did not work in the published package

Docs

None

Description

Supersedes / closes #1300
See also protobufjs/protobuf.js#1499

This area of TypeScript arcana is confusing, but I don't think there is anything about module augmentations that requires them to be in a .d.ts file.

The way it's currently done was generally working, except as pointed out in #1300 we didn't include the typings dir in the published package.

I believe we didn't run into this problem in our own code because we usually turn on "skipLibCheck": true.

[linear]

FG-10163 fix: add typings to package output

[dnikitop]

LGTM. Thanks!

[defunctzombie]

I would not bump the package version in the same PR - a habit I try to avoid should we decide on some other change being part of a new release

[jtbandes]

should we decide on some other change being part of a new release

Even if I intend to release immediately after merging the PR? I find this slows down the ability to release since you have to wait for review again 🤷