chore: override broken @types package to avoid TS bump

[dkundel]

Overriding a package that's incompatible with TS 3.9 (what we are currently using) as it's breaking the CI system. We should upgrade to the latest TypeScript major and pin @types packages respectively but that's a bigger effort.

Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

• I acknowledge that all my contributions will be made under the project's license.

[bnb]

Are these types needed here? It does not seem like this specific package.json has a dependency on Express. Perhaps this is just a part of how Lerna works that I'm not familiar with?

[dkundel]

I don't think it's strictly necessary here. Npm overrides gives me a headache at times and wanted to be extra sure that the wrong version can't be anywhere in the path especially since we run TypeScript typically from the root. There's definitely some overall dependency cleanup we can do.

[bnb]

Are you okay with the override being relative? You're using a tag rather than a version so the version could change out from under you the future.

If so, this LGTM. If not, might want to pin to a specific version (4.17.28 is what the tag currently points to).

[dkundel]

I'm trying to see if tags actually work for this pretty reliably so that in the future we can tag more @types dependencies with the tag rather than version range. If it doesn't work I'll revert to the fixed version.