[FSSDK-11497] fire config update events synchronously

[raju-opti]

Summary

• fire the project config updates synchronously. this will allow the optimizely class to propagate the initial project config synchronously to all sub components. This can be useful when the client is initialized with a datafile. One downside is, the update event handler needs to be registered before calling start() on the config manager, but since we only use the config manager internally, we can maintain that.

Issues

• FSSDK-11497

[Copilot]

Pull Request Overview

This PR updates the project's configuration update flow to fire events synchronously, ensuring the initial configuration is propagated immediately.

• Removed the asynchronous scheduleMicrotask wrapping for update events in the ProjectConfigManager.
• Updated tests to reflect the new synchronous behavior and adjust the timing of manager.start() calls accordingly.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
lib/project_config/project_config_manager.ts	Removed scheduleMicrotask to emit update events synchronously.
lib/project_config/project_config_manager.spec.ts	Adjusted tests to register listeners before start() and reflect synchronous updates.

Comments suppressed due to low confidence (1)

lib/project_config/project_config_manager.ts:167

• Switching to synchronous event emission may block the caller if listeners perform heavy work. Ensure that all update listeners are lightweight or document the synchronous behavior clearly.

scheduleMicrotask(() => {

[coveralls]

coverage: 80.73% (+0.005%) from 80.725%
when pulling 903ca5d on raju/sync_update_config
into 299e1d7 on master.