fix/1529-invalidate-presentation-controls

[nielsvdpol]

Why

Resolves: #1529
When using <Canvas frameloop="demand" />, the PresentationControls component was non-functional because interactions and easing animations did not automatically trigger re-renders. Since frameloop="demand" disables continuous rendering, it requires manual invalidation of the render loop to update the scene. Without this, changes to rotation or scale weren't reflected visually.

This PR fixes that issue by ensuring the component properly invalidates the render loop on interaction and animation updates, restoring expected behavior when frameloop="demand" is in use.

What

• Fixed broken behavior under frameloop="demand" by manually triggering re-renders with invalidate() from useThree.
• Called invalidate():
  • Inside onDrag and onDragEnd gesture handlers to ensure updates apply during/after interactions.
  • Inside the useFrame loop when easing causes a change to rotation or scale.
• This ensures the component works correctly in both default and frameloop="demand" render modes.

Checklist

• Ready to be merged

[vercel]

@nielsvdpol is attempting to deploy a commit to the Poimandres Team on Vercel.

A member of the Team first needs to authorize it.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.