Calling a server action during render tries to update `Router` component, causing an error

### Link to the code that reproduces this issue https://codesandbox.io/p/devbox/crazy-field-gnyj7q ### To Reproduce 1. Visit the reproduction app. 2. In the app preview, see the Next.js error pop-up: > __Console Error__ > > Cannot update a component (`Router`) while rendering a different component (`Demo`). To locate the bad setState() call inside `Demo`, follow the stack trace as described in https://react.dev/link/setstate-in-render Note that there is no explicit `setState()` call inside the component. ### Current vs. Expected behavior Currently, calling a server action during a render causes a React error (see above). The expected behavior is that the server action returns a `Promise` (without causing a React error), and that the `Promise`, if properly cached, can be consumed with `use` (without causing a React error). ### Provide environment information ```bash Operating System: Platform: linux Arch: x64 Version: #1 SMP PREEMPT_DYNAMIC Sun Aug 6 20:05:33 UTC 2023 Available memory (MB): 4102 Available CPU cores: 2 Binaries: Node: 20.9.0 npm: 9.8.1 Yarn: 1.22.19 pnpm: 8.10.2 Relevant Packages: next: 15.2.0-canary.27 // Latest available version is detected (15.2.0-canary.27). eslint-config-next: N/A react: 19.0.0 react-dom: 19.0.0 typescript: 5.3.3 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) Runtime ### Which stage(s) are affected? (Select all that apply) next dev (local), next start (local) ### Additional context _No response_