Add orn-ui

[DavidTrujillo123]

Adds orn-ui at the end of react-native-libraries.json, per the README.

Atomic-design component library for React Native and Expo: 44 typed
components (atoms, molecules, organisms), light/dark theming, zero runtime
dependencies.

Flags I set, and why:

• expoGo: true — there is no native code in the package at all, so it
  runs in Expo Go with no dev client and no prebuild. Verified in CI against
  Expo SDK 54, 55, 56 and 57, each with its own job running tsc plus the
  full test suite against that exact react-native/react pair.
• newArchitecture: true — same reason: no native modules, nothing to
  migrate. Peer range is react-native >= 0.81.
• ios / android — pure JS, works on both.
• web is intentionally left off: it is not tested against
  react-native-web, so I am not claiming it.

dependencies is empty; react, react-native and
react-native-safe-area-context are the only peers.

• Docs: https://orn-ui-docs.vercel.app
• npm: https://www.npmjs.com/package/orn-ui

Disclosure: this is my own library.

🤖 Generated with Claude Code

https://claude.ai/code/session_015HDDSem6KnSEXvUPGAsaSM

[DavidTrujillo123]

Heads up: the red check is from 1f2b3fd, which is no longer the head of this PR.

The validator was right — githubUrl pointed at the repository root, which is
the pnpm workspace root and is marked "private": true. It is not the published
package.

7d9a021 points it at packages/ui instead, per the monorepo note in the
README. That is the package published to npm as orn-ui:

name: orn-ui | private: false | version: 0.2.7

CI has not re-run on the new commit, so the failing check shown here predates
the fix. Happy to rebase or close/reopen if that helps trigger a fresh run.

[Simek]

Hey @DavidTrujillo123, thanks for adding a new entry to the directory! 👍