chore: add a changeset for the stylis middleware migration

Covers what a consumer actually receives relative to the frozen Fuselage 0.31.25
release: the shorthand-splitting fix, the physical expansion of `inset`, the
`stylis` peer range, and the CommonJS declarations dropped from the tarball. The
build, lint and test wiring is not published, so it is left out, as is the ESM
emit fix — 0.31.25 already shipped correct ESM, so that regression was introduced
and fixed inside this branch and nets to nothing downstream.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: tassoevan

.changeset/stylis-logical-props-middleware-monorepo-migration.md

@@ -0,0 +1,13 @@
+---
+'@rocket.chat/stylis-logical-props-middleware': patch
+---
+
+Moved `@rocket.chat/stylis-logical-props-middleware` into the Rocket.Chat monorepo, continuing from the frozen Fuselage 0.31.25 release.
+
+Fixed logical shorthands that take one value per side losing their declarations entirely on the fallback path. `margin-inline: 4px 8px` expanded to `margin-left: 4px 8px` and `margin-right: 4px 8px`, and since two values on a longhand is invalid, browsers without logical property support dropped both — the element ended up with no inline margin at all rather than the wrong spacing. The value is now split across the two sides, covering `margin-inline`, `padding-inline`, `inset-inline`, their block counterparts, and `border-{inline,block}-{width,style,color}`. Splitting happens on top-level whitespace only, so values nested in `calc()`, `var()` and friends stay intact, and an `!important` flag is reattached to every expansion.
+
+`inset` carried the same defect behind a direction flip it should never have had, having been routed through the inline and block axes. It is a physical shorthand, so it now expands straight to `top`, `right`, `bottom` and `left` in the usual 1-to-4 value box order.
+
+The `stylis` peer dependency moves from the exact `4.0.10` pin to `~4.4.0`, the version the monorepo resolves.
+
+The CommonJS build no longer ships a duplicate copy of the type declarations, leaving `dist/esm` as the single source of types — where `types` already pointed.