fix: prevent mixing responsive viewport keys with T's keys in Responsive<T>

[te6-in]

Hi, first of all, congrats on and thanks for opensourcing reshaped, really enjoying digging the codebase.

I noticed a small type safety gap in Responsive<T> and wanted to contribute a fix.

Summary

Regarding ResponsiveOnly<T>, currently when T is an object like ButtonProps, it allows mixing T's keys with viewport keys without a type error.

const buttonProps = useResponsiveClientValue<ButtonProps>({
  s: { variant: "solid" },
  xl: { variant: "outline" },
  onClick: () => {},  // no error
});

This PR adds an intersection to ResponsiveOnly<T> so that T's own keys would be mapped to never.

Related Issue

not found so far

Notes for Reviewers

While this makes codes like above make type error, IDE still suggests T's keys in autocompletions. I guess this is a TypeScript limitation.

[blvdmitry]

Hey, thanks for the PR, do you have a reproduction of this on TS playground as well? Can't reproduce this issue locally or in the playground myself:
https://www.typescriptlang.org/play/?ssl=10&ssc=1&pln=14&pc=4#code/KYDwDg9gTgLgBDAnmYcBqBLYB3Ss4C8cARAM7FwA+JAthdcQDb0kjMDcAsAFCh7xIUcAErBSkAHakMAN2AB5CY0QAeACoA+QnADecANoBrYIjgYJ6LLmgwAugH4AXHDVwAvl249BqAEIBXGBgICQAFKAgwUm0dHjg4GQBDKAxEiRhnUhgUiQBzHjceHgAzfwkAYxgMELh-UmBRcRDpOQBhRix0tETGf2B1DQAKGWdGyRaFJVVNAEpdQq9ucub4ACNA4LCIqO06hrFx2WB2zphu3v6AoJDwyNIh2O540mc9JJS0jJJSCA6AEwobgANHE4GxXglkql0s5iBBAh0JMBASCnnAQidyoZnIM5gQtDpgfEAPTEuASCBwYBQCJQAozdhAA

[te6-in]

@blvdmitry Hey sure, Playground

• added type Responsive<T> = T | ResponsiveOnly<T> to reproduce the issue
• used variant instead of onClick since onClick doesn't exist in ButtonProps in the playground example