Optimizations for alias tests which are flaky and timeout

[agarwal-navin]

There are a couple of aliasing end-to-end tests that are flaky and intermittently time out. See AB#31828 and AB#31831. This PR attempts to fix that by optimizing a couple of steps and fixing a bug:

1. In beforeEach, the test waits for container connection and calls provider.ensureSynchronized. Both of these are not needed so removing them.
2. In Assign multiple data stores to the same alias, first write wins, different containers, a provider.ensureSynchronized is not needed so removing it.
3. In Assign multiple data stores to the same alias, first write wins, different containers from snapshot there is a bug where the test expects the summarizer to summarize the data store that was created and aliased. However, that may not happen because the provider.ensureSynchronized is called before the summarizer is created - it should be called after.
   Also, the test object provider needs to be created with syncSummarizer: true option for it to sync changes to the summarizer client.
4. Changed the awaits in the flaky tests to timeoutAwait so it's more debuggable.

PR Overview

This PR addresses flaky and intermittent timeouts in aliasing end‐to‐end tests by removing unnecessary synchronization calls and fixing a bug in the summarizer initialization order. Key changes include:

• Removing waitForContainerConnection and an extra provider.ensureSynchronized call in the beforeEach block.
• Adding the syncSummarizer: true option when getting the test object provider.
• Reordering the provider.ensureSynchronized call after creating the summarizer in one test to ensure proper summarizer synchronization.

Reviewed Changes

File	Description
packages/test/test-end-to-end-tests/src/test/rootDatastores.spec.ts	Removed redundant synchronization calls and reordered summarizer initialization to fix a bug

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (2)

packages/test/test-end-to-end-tests/src/test/rootDatastores.spec.ts:337

• [nitpick] The provider.ensureSynchronized() call has been moved after creating the summarizer to address a timing bug. Consider adding an inline comment here to clarify the importance of this ordering for future maintainers.

await provider.ensureSynchronized();

packages/test/test-end-to-end-tests/src/test/rootDatastores.spec.ts:46

• [nitpick] The introduction of the syncSummarizer: true option in the test object provider should be validated to ensure it doesn't introduce unintended delays or race conditions. It would be beneficial to add or update tests that cover the summarizer synchronization behavior.

provider = getTestObjectProvider({