test(contact-center-insights): add delay to createAnalysis test to ensure conversation readiness

[angelcaamal]

Description

This PR addresses a race condition found in the createAnalysis test. Due to the asynchronous nature of the backend ingestion process, the conversation was occasionally not fully ready to be analyzed, resulting in internal errors.

Fixes #

Note: Before submitting a pull request, please open an issue for discussion if you are not associated with Google.

Checklist

• I have followed guidelines from CONTRIBUTING.MD and Samples Style Guide
• Tests pass: npm test (see Testing)
• Lint pass: npm run lint (see Style)
• Required CI tests pass (see CI testing)
• These samples need a new API enabled in testing projects to pass (let us know which ones)
• These samples need a new/updated env vars in testing projects set to pass (let us know which ones)
• This pull request is from a branch created directly off of GoogleCloudPlatform/nodejs-docs-samples. Not a fork.
• This sample adds a new sample directory, and I updated the CODEOWNERS file with the codeowners for this sample
• This sample adds a new sample directory, and I created GitHub Actions workflow for this sample
• This sample adds a new Product API, and I updated the Blunderbuss issue/PR auto-assigner with the codeowners for this sample
• Please merge this PR for me once it is approved

Note: Any check with (dev), (experimental), or (legacy) can be ignored and should not block your PR from merging (see CI testing).

[gemini-code-assist]

Code Review

This pull request introduces a 10-second delay in the createAnalysis.test.js file to ensure conversations are ready before analysis. Feedback suggests replacing the raw setTimeout with the project's existing delay helper function to maintain consistency and leverage its built-in backoff logic.

[gemini-code-assist]

Instead of using a raw setTimeout, consider using the existing delay helper function defined at the top of this file. This ensures consistency with the rest of the test file and leverages the built-in exponential backoff logic if the test retries after a failure.

Suggested change

	await new Promise(resolve => setTimeout(resolve, 10000));
	await delay(this.test, 10000);

References

1. Maintain established boilerplate patterns across samples within a repository, even if it means deviating from technically optimal solutions.