fix(cli): prevent --log-level=value from swallowing next argument

[LikiosSedo]

Summary

When using --log-level=debug (equals syntax), the SetLogLevel handler incorrectly strips the next argument too.

Root Cause

The argument filter loop checks isLogLevelArg(args[i - 1]), which matches the combined form --log-level=debug. This causes the argument at i (the one after the log-level flag) to be skipped.

args: ["--log-level=debug", "--name=hello"]

i=0: "--log-level=debug" → isLogLevelArg matches → skip (correct)
i=1: "--name=hello" → isLogLevelArg(args[0]) matches "--log-level=debug" → skip (BUG)

Fix

Change the look-back check from isLogLevelArg(args[i - 1]) to args[i - 1] === "--log-level". This ensures only the space-separated value (e.g. debug after --log-level debug) is skipped, not the argument following a combined --log-level=value form.

Reproduction

// --log-level=debug --name=hello → name = None (bug)
// --log-level debug --name=hello → name = Some("hello") (works)

Fixes #6103

[changeset-bot]

🦋 Changeset detected

Latest commit: 0649275

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@effect/cli	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[IMax153]

@LikiosSedo - we will need a few test cases added to the CLI test suite to prevent further regressions. Once added, I can trigger CI.