feat: introduce excludeDeprecated option

[benevbright]

Changes

Often time we want to exclude deprecated fields completely from generated types so we can spot deprecated fields asap.
Unfortunately, TS doesn't have a such option: microsoft/TypeScript#49433
The code editor shows deprecated fields with scratched out, which is nice but not enough.

For example, you created a new version of SDK, then you wish TS would complain about use of deprecated fields asap but it doesn't.

How to Review

It should be straight forward to review but I'm not sure if I should add this option on every single getEntries usages.

Checklist

• Unit tests updated
• README updated
• examples/ directory updated (if applicable)

[changeset-bot]

⚠️ No Changeset found

Latest commit: b03036d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[drwpow]

This is a cool idea, thank you! I’m in favor of merging this as this seems useful and spiritually-aligned with the deprecated property. No feedback on the PR—everything looks well-considered and reasonable. Great tests, flag addition, everything 🎉

[benevbright]

@drwpow super! thanks! 👍

I just added README as well. (could you approve again?)

[mitchell-merry]

love it