fix(datepicker): added waitFor() to react.lazy test

[jt-helsinki]

Closes #15701

{{short description}}

Changelog

New

• {{new thing}}

Changed

• {{change thing}}

Removed

• {{removed thing}}

Testing / Reviewing

{{ Add descriptions, steps or a checklist for how reviewers can verify this PR works or not }}

[jt-helsinki]

fixes: #15701

[netlify]

✅ Deploy Preview for v11-carbon-react ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	7fc9156
🔍 Latest deploy log	https://app.netlify.com/sites/v11-carbon-react/deploys/65c2373e8bd1850008f8117e
😎 Deploy Preview	https://deploy-preview-15702--v11-carbon-react.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for v11-carbon-react ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	f3f3ace
🔍 Latest deploy log	https://app.netlify.com/sites/v11-carbon-react/deploys/65c2466ace2cc20008947efe
😎 Deploy Preview	https://deploy-preview-15702--v11-carbon-react.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[tay1orjones]

Hey thanks for opening this, could you outline how this helps the test? The RTL docs state that findBy* queries are a combination of getBy queries and waitFor, the waitFor options are the last argument.

I think this change will cause a warning to pop during the the lint ci check - eslint-plugin-testing-library is configured to be ran on these files:

carbon/config/eslint-config-carbon/plugins/testing-library.js

Lines 14 to 21 in 0ee6ff9

	extends: ['plugin:testing-library/react'],
	files: ['packages/react/**/*-test.js'],
	rules: {
	'testing-library/no-node-access': [
	'error',
	{ allowContainerFirstChild: true },
	],
	},

This preset enables the prefer-find-by rule, which typically warns on usages like this.

[jt-helsinki]

@tay1orjones

Yes, you're right. What I added wasn't quite right. I've updated this to add the timeout directly to the call to findByLabelText().

[tay1orjones]

Awesome, thanks!