feat(require-types): add new rule

[michaelfaith]

PR Checklist

• Addresses an existing open issue: fixes 🚀 Feature: Bring in a require-types rule #816
• That issue was marked as status: accepting prs
• Steps in CONTRIBUTING.md were taken

Overview

This change adds a new require-types rule.

Closes #816

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.50%. Comparing base (4208603) to head (42ed2ee).
Report is 11 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #958      +/-   ##
==========================================
+ Coverage   98.77%   99.50%   +0.73%     
==========================================
  Files          21       20       -1     
  Lines        1222     1223       +1     
  Branches      142      142              
==========================================
+ Hits         1207     1217      +10     
+ Misses         15        6       -9     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[JoshuaKGoldberg]

Looks great to me! Just one suggestion on docs, WDYT?

🚀

[JoshuaKGoldberg]

[Non-Actionable] From https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html:

Note that the "typings" field is synonymous with types, and could be used as well.

Confirmed that "types" is the primary one. I don't adding opt-in support for "typings" is required for the base rule. If someone really wants that they can file an issue explaining why. 👍

[github-actions]

🎉 This is included in version v0.29.0 🎉

The release is available on:

• GitHub releases
• npm package (@latest dist-tag)

Cheers! 📦🚀