fix: handle argument value replacement with more patterns

[calmini]

argument value replacement by user input with specific patterns
add --API_KEY==YOUR_API_KEY -> --API_KEY={USER_INPUT_VALUE}
add --API_KEY YOUR_API_KEY -> --API_KEY {USER_INPUT_VALUE}

directly replace env variable value with user input value regardless the env variable value pattern(${VAR},VAR,{VAR},...)

[github-actions]

Semantic Version Check

⚠️ No semantic version changes detected.

Please ensure your commits follow the Conventional Commits format:

• feat: new feature (triggers MINOR version bump)
• fix: bug fix (triggers PATCH version bump)
• BREAKING CHANGE: description (triggers MAJOR version bump)

[niechen]

I think we should still clean up repo server jsons because there might be other programs using these json artifacts. better to keep them clean and organized.

[github-actions]

Semantic Version Check

⚠️ No semantic version changes detected.

Please ensure your commits follow the Conventional Commits format:

• feat: new feature (triggers MINOR version bump)
• fix: bug fix (triggers PATCH version bump)
• BREAKING CHANGE: description (triggers MAJOR version bump)

[calmini]

I think we should still clean up repo server jsons because there might be other programs using these json artifacts. better to keep them clean and organized.

Yep, makes sense — this PR tries to be backward-compatible with existing --arg=VAR or --arg VAR patterns found in some server JSONs, perhaps keeping ${VAR} pattern as the recommended format for latter registered servers or introduce a linting tool to keep arguments definition unified.