fix(remix-dev): don't allow unknown fields in TS future config

[brophdawg11]

Closes #7253

See approach in https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBAbzgUQB4EMDG8C+cBmUEIcA5DAJ5gCmAtPtQM4ykDcAUO8AHYzVT4s1OADEArjDFRqAYQjd8wAOaJ2ASABuAZgD6UdABMR1dJOkBGAFxwARhAgAbE93Xa9h46anUATNbuOzuw4nDx8AkJwAIJgYHIKyqpwyQQS3gD81gAK6LDA6A4APOJmsvKKSgB8cABkiADaYERgAHLoINTWzFA8SgC61tzUGvxwISHs1KiQsHAG1IJiDvAI6vhp0tarapq6+kYmpVZwMFBi1AA06po+OgDuMAAW1JgA1tan51dqOFd4jKZgIxFExorF4hV2EA

We could have also used Exact from type-fest but it felt weird needing 2 args and doing:

future: Exact<Partial<FutureConfig>, Partial<FutureConfig>>

Note this is in addition to the build-time warnings we log for JS config files: https://github.com/remix-run/remix/blob/dev/packages/remix-dev/config.ts#L566

[changeset-bot]

⚠️ No Changeset found

Latest commit: ea853f8

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

[github-actions]

🤖 Hello there,

We just published version 2.0.0-pre.0 which includes this pull request. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!