both router and react 19 were modifying the Promise object in a similar manner which caused a conflict.
See https://github.com/facebook/react/blob/v19.0.0/packages/react-reconciler/src/ReactFiberThenable.js#L162-L228 for how React 19 modifies the Promise object.
Both used an additional `status` property to track the Promise status, but router was using the value "success" and React was using the value "fulfilled" to mark a fulfilled Promise.
This change stores the router specific Promise tracking values using a symbol to avoid any potential collision.
fixes#2953
* docs: gfm alerts on the deprecated apis
* docs: gfm alerts in the api reference
* docs: gfm alerts in framework/react
* docs: gfm alerts in framework/react/guide
* docs: more gfm alerts in the api reference
* docs: update to the decisions on dx doc
* docs: path-params
* docs: search params
* docs: type-safety
* docs: useParams reference
* docs: code-based routing
* docs: data mutations
* docs: route-trees
* docs: search-params
* docs: deferred-data-loading
* docs: revert unneccessary changes and leave in a stub to add the "tips"
* docs: forgot to include in the last commit
* docs: add the "🧠 Quick tip" items about the `getRouteApi` function