Fix lint error: Remove async keyword from useMemo callback

[Wintus]

Summary

• Fixed ESLint error in PageTitleInput.tsx where useMemo callback was using async keyword
• Rewrote the async function to return a Promise using .then()/.catch() pattern instead
• Added documentation comment explaining the linter rule and rationale

Details

The React compiler doesn't allow async functions as useMemo callbacks. While semantically equivalent, React prefers explicit Promise returns to make it clear the callback itself runs synchronously even though it returns async work.

see https://github.com/facebook/react/blob/v19.2.0/compiler/packages/babel-plugin-react-compiler/src/Validation/ValidateUseMemo.ts#L90-L105

The ESLint has started alerting this since v7

• chore(deps-dev): bump eslint-plugin-react-hooks from 5.2.0 to 7.0.0 #122
• https://github.com/facebook/react/blob/main/packages/eslint-plugin-react-hooks/CHANGELOG.md#700

Changes

• Converted useMemo(async () => {...}) to useMemo(() => Promise.resolve(...).then())
• Added clarifying comment about the linter rule requirement

Test plan

• npm run lint passes without errors
• Existing tests still pass

🤖 Generated with Claude Code