make changes to enable moving `TokenamiPropertiesPick/Omit` to public facing APIs

the css utility use case is intended to be similar to tailwind-merge, so the idea is that it would only be used when merging style rules (and directly on native elements).

the rest of the codebase can style in the style attribute directly if the component uses the TokenamiStyle type to enable tokenami properties on that component.

atm, that type also allows the css utility to be passed to the style attribute which is fine rn, but i'd like to expose the TokenamiPropertiesPick and TokenamiPropertiesOmit types so that consumers can narrow the properties their component accepts.

the TokenamiCSS type returned by the css utility is effectively {} which bypasses any type checking, so passing it to a comp with narrowed properties would be allowed. this aims to improve that type checking experience.

try to get TokenamiCSS to infer the returned properties. i already attempted that and it opened a can of worms but perhaps a fresh set of eyes can crack it.

No files or tests are named. Start by tracing the public type definitions for TokenamiCSS, TokenamiPropertiesPick, and TokenamiPropertiesOmit, then reproduce the interaction between the css utility and a component with narrowed style properties. Done means TokenamiCSS infers its returned properties and narrowed components reject incompatible values.