Fix environment variable parsing for comma-separated values in CLI

[Siddhant-K-code]

Problem

Environment variables with comma-separated values (e.g., COMPOSE_PROFILES=value1,value2,value3) were displaying the scope pattern (*/*) instead of the actual values when using gp env.

Root cause

The parseArgs function in cmd/env.go had incorrect string splitting logic:

kv := strings.SplitN(arg, "=", 1)

Using a limit of 1 prevents any splitting, so "KEY=value" returns ["KEY=value"] as a single element.

Solution

• Changed strings.SplitN(arg, "=", 1) to strings.SplitN(arg, "=", 2)
• Simplified validation logic by removing redundant checks
• Preserved all existing functionality and error handling

Fixes CLC-1662

[mustard-mh]

LGTM