fix: Report data source state as valid after bootstrap (#1203)

<!-- CURSOR_SUMMARY -->
> [!NOTE]
> **Low Risk**
> Low risk: a small state-reporting change limited to the bootstrap
identify path, covered by an updated unit test asserting the
`dataSourceStatus` event.
> 
> **Overview**
> When `identify` completes using `bootstrap` data, `BrowserDataManager`
now explicitly reports the data source status as **valid** by calling
`dataSourceStatusManager.requestStateUpdate(DataSourceState.Valid)`.
> 
> The bootstrap identify unit test is updated to assert that a
`dataSourceStatus` event is emitted with `state: 'VALID'` after
bootstrap initialization.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
6d3276f. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Author: kinyoklion

packages/sdk/browser/__tests__/BrowserDataManager.test.ts

@@ -396,6 +396,10 @@ describe('given a BrowserDataManager with mocked dependencies', () => {
     });
     expect(platform.requests.createEventSource).not.toHaveBeenCalled();
     expect(platform.requests.fetch).not.toHaveBeenCalled();
+    expect(emitter.emit).toHaveBeenCalledWith(
+      'dataSourceStatus',
+      expect.objectContaining({ state: 'VALID' }),
+    );
   });
 
   it('should identify from polling when there are no cached flags', async () => {

packages/sdk/browser/src/BrowserDataManager.ts

@@ -196,6 +196,7 @@ export default class BrowserDataManager extends BaseDataManager {
       bootstrapParsed = readFlagsFromBootstrap(this.logger, browserIdentifyOptions.bootstrap);
     }
     this.flagManager.setBootstrap(context, bootstrapParsed);
+    this.dataSourceStatusManager.requestStateUpdate(DataSourceState.Valid);
     this._debugLog('Identify - Initialization completed from bootstrap');
     identifyResolve();
   }