docs(philosophy): clarify 'Three.js framework adapters' to 'Three.js renderers' (#2251)

In the 'Controlled is Cool' section, the bullet on Non-DOM support said
'Three.js framework adapters'. Three.js is not a framework - it's a
WebGL rendering library. The intended meaning was that TanStack Form's
controlled-component approach works with non-DOM renderers, including
Three.js. Replaced 'framework adapters' with 'renderers' to be accurate.

Co-authored-by: Carlos Jimenez <cjimenez@r21digital.com>

Author: kushaim

docs/philosophy.md

@@ -33,7 +33,7 @@ This comes with a number of advantages:
 
 - **Predictable**: You can predict the state of your form at any point in time.
 - **Easier testing**: You can easily test your forms by passing in values and asserting on the output.
-- **Non-DOM support**: You can use TanStack Form with React Native, Three.js framework adapters, or any other framework renderer.
+- **Non-DOM support**: You can use TanStack Form with React Native, Three.js renderers, or any other framework renderer.
 - **Enhanced conditional logic**: You can easily conditionally show/hide fields based on the form state.
 - **Debugging**: You can easily log the form state to the console to debug issues.