Fix flaky BrowserSimulation test: async timing in ObjectForm field validation

[Copilot]

The Scenario 4: Object Create Form test was failing in CI with expected 0 to be greater than 0 when checking for the Date field label. The test was racing against async form rendering (client init + schema fetch + field generation).

Changes

MockDataSource interface completion

• Added missing findOne method required by DataSource interface

Async timing adjustments

• Increased initial field wait from 5s → 10s to account for 500ms client init delay + async operations
• Changed sequential field validation loop to concurrent Promise.all (reduces max wait from 35s → 10s)

Code quality

• Extracted expectLabelToExist helper to eliminate duplication

// Before: synchronous checks that race against rendering
for (const label of fieldLabels) {
  expect(screen.queryAllByText(new RegExp(label, 'i')).length).toBeGreaterThan(0);
}

// After: concurrent async checks with proper timeout
await Promise.all(
  fieldLabels.map(label =>
    waitFor(() => expectLabelToExist(label), { timeout: 5000 })
  )
);

All changes are test-only. No production code modified.

Original prompt

引用: https://github.com/objectstack-ai/objectui/actions/runs/21622660842/job/62315046887#step:8:1

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
objectui	Ready	Preview, Comment	Feb 3, 2026 9:12am
objectui-components	Ready	Preview, Comment	Feb 3, 2026 9:12am
objectui-crm-app	Error		Feb 3, 2026 9:12am

[github-actions]

✅ All checks passed!

• ✅ Type check passed
• ✅ Tests passed
• ✅ Lint check completed

[Copilot]

Pull request overview

This PR fixes a flaky test in the CI pipeline that was failing due to race conditions in async form rendering. The test was checking for form field labels before they were fully rendered, causing intermittent failures with "expected 0 to be greater than 0" errors.

Changes:

• Added missing findOne method to MockDataSource to complete the DataSource interface implementation
• Increased timeout from 5s to 10s and converted sequential field checks to concurrent Promise.all for better async handling
• Extracted expectLabelToExist helper function to eliminate code duplication

[Copilot]

The findOne method signature should match the DataSource interface exactly. The interface defines id parameter as string | number, but the mock only accepts string. While this works for current tests, it could cause type errors if future tests pass numeric IDs. Consider updating the signature to match the interface.

Suggested change

	async findOne(objectName: string, id: string) {
	async findOne(objectName: string, id: string | number) {