fix: sync Composite values with Lottie schema

[Aidosmf]

Summary

• correct Composite stacking values to Below = 1 and Above = 2
• keep the modern namespace constants and deprecated Composite.VALUE aliases in sync
• add exact runtime and literal-type regression coverage
• add a patch changeset

Context

The formal lottie-spec 1.0.1 schema does not yet define repeaters or Composite. This focused correction follows the exhaustive Lottie Docs schema and its corrected mapping: https://github.com/LottieFiles/lottie-docs/blob/main/schema/constants/composite.json

Validation

• yarn test
• yarn changeset status --since=origin/main
• git diff --check origin/main...HEAD

[changeset-bot]

🦋 Changeset detected

Latest commit: 13ad1e4

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@lottie-animation-community/lottie-types	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[kudanai]

Verified against lottie-docs schema/constants/composite.json (1=Below, 2=Above) — matches. The deprecated Composite.VALUE enum references the constants so it auto-syncs, the repeater m?: Composite.Value field is unaffected, and both runtime (assert-constants.cjs) and literal-type (types.ts) coverage are updated. This is the exact follow-up flagged on #19. LGTM 🚀