fix(home): unify new project button labels - #3521

Summary

The Home header said “New project” while the empty-project action said “Create project”, although both open the same form. Reuse t('New project') for both entry buttons (简体中文：新建项目) and update the existing render-test assertions.

Scope existing E2E entry locators to the Home header: identical labels otherwise make page-wide Playwright locators ambiguous. Keep import-dialog and menu-item locators unchanged. Add English and Simplified Chinese browser coverage that opens and cancels the form through each of the two same-name entry buttons.

Existing translations cover all eight locales. The project form's submit action and all click handlers remain unchanged. No historical-data compatibility, enum/state, persistence, dependency, or public-interface changes.

Validation

Checks run after the last material edit:

• Entry labels, opening/cancelling the form from either entry, and loading/error/populated states + locale integrity → npx vitest run src/renderer/src/pages/home/HomePage.render.test.tsx src/renderer/src/i18n/resources.test.ts --maxWorkers=2 → 829 tests passed.
• Renderer types → package build and npm run typecheck:web:compiled → passed.
• Formatting → Prettier on all changed files → passed.
• Same-name entry behavior and existing tooltip/form interactions → npx playwright test --config e2e/playwright.browser.config.ts e2e/browser/button-feedback.spec.ts e2e/browser/hover-bubble.spec.ts e2e/browser/row-hit-targets.spec.ts → 51 passed. The Home tooltip test reproduced the strict-mode failure before scoping its locator and passed afterward.
• Source lint → npm run lint → passed.
• CI bootstrap failure follow-up → npx vitest run src/renderer/web/bootstrap.test.ts -t 'uses the desktop particle loader' --maxWorkers=1 → passed without changes. The earlier CI failure occurred while waiting for bootstrap API initialization, before Home renders.
• Committed-diff impact → npm run test:affected:explain -- --base origin/main --head HEAD → full fallback because the classifier treats the changed Electron E2E files as unknown ownership. Per the maintainer's explicit instruction, full validation is delegated to PR CI instead of running the full suite locally. The current worktree CodeGraph confirms both entries call openCreateDialog; production ownership remains page_home.

Additional module evidence after the final production edit: npm run test:module -- page_home / its module runner passed 92 files and 3558 tests. A concurrent run hit the existing 15-second LiteratureLibraryPage later-import-batch-failure timeout (3557 passed); its isolated rerun passed without changes. Subsequent edits affect only E2E locators and browser tests.

Independent review of the final E2E changes found no actionable issues. Existing files and imports are preserved, so module registration changes are unnecessary. The full local suite was intentionally omitted as requested. Chromium checks cover the shared renderer; native Windows journeys are delegated to the latest PR CI. No local Electron/platform certification is claimed.