Fix TS package not to override base no-restricted-syntax selectors

[mcmire]

Both the eslint-config and eslint-config-typescript packages list the no-restricted-syntax rule. But eslint-config-typescript overwrites the selectors that eslint-config specifies, meaning that some invalid syntax is not detected in TypeScript files that would ordinarily be detected in JavaScript files. This commit ensures that the two are always kept in sync.

Fixes #434.

---

Note

Medium Risk
Changes TypeScript linting behavior by re-enabling base no-restricted-syntax selectors (with, in, sequence expressions), which can introduce new lint failures across TS codebases. The merge logic is small but relies on correctly collecting/ordering rule options from the base flat config.

Overview
Fixes @metamask/eslint-config-typescript so it no longer silently overwrites the base no-restricted-syntax configuration in flat config mode.

The TypeScript config now imports the base config and programmatically collects/extends its array-valued rule options, ensuring TS files also forbid with statements, the in operator, and sequence expressions while still adding the TypeScript-specific restriction against TS private modifiers.

Updates the TypeScript package rules-snapshot.json and documents the (breaking) linting fix in the TypeScript changelog.

^{Written by Cursor Bugbot for commit 107bcfe. This will update automatically on new commits. Configure here.}

[mcmire]

We shouldn't have been overriding these rules, but it's been a while since we made a new eslint-config release, so even though I don't like that we have to mark this change as breaking, I figure it's probably better to do so than not.

[mcmire]

I could also wait to merge this if there are any non-breaking changes we'd like to release first.