fix: use consistent `framer-motion` semver range · sanity-io/sanity@d018b20

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ref values (the `current` property) may not be accessed during render. (https://react.dev/reference/react/useRef)

Ref values (the `current` property) may not be accessed during render. (https://react.dev/reference/react/useRef)

Ref values (the `current` property) may not be accessed during render. (https://react.dev/reference/react/useRef)

Ref values (the `current` property) may not be accessed during render. (https://react.dev/reference/react/useRef)

Reassigning a variable after render has completed can cause inconsistent behavior on subsequent renders. Consider using state instead

Ref values (the `current` property) may not be accessed during render. (https://react.dev/reference/react/useRef)

Ref values (the `current` property) may not be accessed during render. (https://react.dev/reference/react/useRef)

Ref values (the `current` property) may not be accessed during render. (https://react.dev/reference/react/useRef)

Ref values (the `current` property) may not be accessed during render. (https://react.dev/reference/react/useRef)

Ref values (the `current` property) may not be accessed during render. (https://react.dev/reference/react/useRef)

Provide feedback