Fix logging test (#4077)

* Fix logging test

* Add comment to explain

* Make test run conditionally

* Merge remote-tracking branch 'origin/master' into fix-logging-test

Author: am1r021

packages/client/test/logging.spec.ts

@@ -33,9 +33,8 @@ describe('[Logging]', () => {
     }
   })
 
-  // This test breaks for no obvious reason and we don't run it in CI anyway.
-  // Running the client confirms that logging is using correct color schemes.
-  it.skip('should colorize key=value pairs', () => {
+  // must be run with `FORCE_COLOR='1' npx vitest test/logging.spec.ts`
+  it.skipIf(process.env.FORCE_COLOR !== '1')('should colorize key=value pairs', () => {
     if (process.env.GITHUB_ACTION !== undefined) {
       assert.isTrue(true, 'no color functionality in ci')
       return
@@ -44,9 +43,15 @@ describe('[Logging]', () => {
       level: 'info',
       message: 'test key=value',
     }) as any
-    assert.strictEqual(
-      message,
-      'test \x1B[38;2;0;128;0mkey\x1B[39m=value ', // cspell:disable-line
+
+    // matches either ESC[32m (basic green) or ESC[38;2;0;128;0m (true-color green)
+    function hasGreen(str: string): boolean {
+      // eslint-disable-next-line
+      return /\x1B\[(?:32|38;2;0;128;0)m/.test(str)
+    }
+
+    assert.isTrue(
+      hasGreen(message), // cspell:disable-line
       'key=value pairs should be colorized',
     )
   })