"Lazy initial state" is actually greedy

Is there any good reason to call the useState(() => ...) feature "Lazy initial state"? The actual implementation is synchronous ("greedy") as far as I can tell, so I would propose to rename it to "Functional initial state" (for consistency with "Functional updates").

• docs: https://reactjs.org/docs/hooks-reference.html#lazy-initial-state
• implementation: https://github.com/facebook/react/blob/02da938fd51f6345ca185d571ea6628189ae81a7/packages/react-reconciler/src/ReactFiberHooks.new.js#L1135-L1142

Related "Lazy initialization" in useReducer section => I would propose "Initialization function"

• docs: https://reactjs.org/docs/hooks-reference.html#lazy-initialization
• implementation: https://github.com/facebook/react/blob/02da938fd51f6345ca185d571ea6628189ae81a7/packages/react-reconciler/src/ReactFiberHooks.new.js#L646-L657

I can make a PR unless someone points out some aspect of the naming that I missed.

從 issue 中連結的 Hooks 參考部分開始：「lazy initial state」和「lazy initialization」。將它們的術語與所參照的實作 ReactFiberHooks.new.js 以及「Functional updates」的措辭進行比較。完成的標準是審查文件術語，並在兩個部分中一致地套用任何已達成共識的命名。