Fix stream_type.test.ts on CI env

[noCharger]

Context:

FAIL  packages/osd-config-schema/src/types/stream_type.test.ts
  ● #defaultValue › returns default when undefined

    expect(received).toMatchInlineSnapshot(snapshot)

    Snapshot name: `#defaultValue returns default when undefined 1`

    - Snapshot  - 0
    + Received  + 1

      Stream {
        "_events": Object {},
        "_eventsCount": 0,
        "_maxListeners": undefined,
    +   "domain": null,
      }

      69 |   test('returns default when undefined', () => {
      70 |     const value = new Stream();
    > 71 |     expect(schema.stream({ defaultValue: value }).validate(undefined)).toMatchInlineSnapshot(`
         |                                                                        ^
      72 |       Stream {
      73 |         "_events": Object {},
      74 |         "_eventsCount": 0,

      at Object.<anonymous> (packages/osd-config-schema/src/types/stream_type.test.ts:71:72)

Wasn't able to reproduce it on local env

yarn test:jest packages/osd-config-schema/src/types/stream_type.test.ts
yarn run v1.22.19
$ node scripts/jest packages/osd-config-schema/src/types/stream_type.test.ts
 PASS  packages/osd-config-schema/src/types/stream_type.test.ts
  ✓ returns value by default (4 ms)
  ✓ Readable is valid (1 ms)
  ✓ Writable is valid (1 ms)
  ✓ Passthrough is valid (1 ms)
  ✓ is required by default (10 ms)
  ✓ includes namespace in failure (2 ms)
  ✓ returns error when not a stream (4 ms)
  #defaultValue
    ✓ returns default when undefined (2 ms)
    ✓ returns value when specified (1 ms)
 
Test Suites: 1 passed, 1 total
Tests:       9 passed, 9 total
Snapshots:   6 passed, 6 total
Time:        3.137 s
Ran all test suites matching /packages\/osd-config-schema\/src\/types\/stream_type.test.ts/i.
✨  Done in 7.99s.

isolated jest config and test on forked repo https://github.com/elastic-analytics/OpenSearch-Dashboards/pull/27/files

[zhongnansu]

I see the PR from feature branch to main branch gets merged and CI passed there. Can we resolve this? Also curious what kind of fix you have done. @kristenTian

[zhongnansu]

stale. Since feature merged to main. I assume this issue is no longer valid. Closing