CLI parse errors for quoted strings

[vinckr]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my Ory Cloud project.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Describe the bug

Not all of the examples displayed in the CLI help are working:

Examples:
ory patch project ecaaa3cb-0730-4ee8-a6df-9553cdfeef89 \
	--replace '/name="My new project name"' \
	--add '/services/identity/config/courier/smtp={"from_name":"My new email name"}' \
	--replace '/services/identity/config/selfservice/methods/password/enabled=false' \
	--delete '/services/identity/config/selfservice/methods/totp/enabled'

the --replace and --add examples that have "quoted" strings in them lead to a parse error. the other examples work fine.

Reproducing the bug

ory patch project 650fbb1c-a376-45a2-b56c-cdf1ec2d1c74 \
	--add '/services/identity/config/courier/smtp={"from_name":"My new email name"}'

leads to

invalid argument "/services/identity/config/courier/smtp={\"from_name\":\"My new email name\"}" for "--add" flag: parse error on line 1, column 41: bare " in non-quoted-field

---

ory patch project 650fbb1c-a376-45a2-b56c-cdf1ec2d1c74 \
	--add "/services/identity/config/courier/smtp={\"from_name\":\"My new email name\"}"

leads to

invalid argument "/services/identity/config/courier/smtp={\"from_name\":\"My new email name\"}" for "--add" flag: parse error on line 1, column 41: bare " in non-quoted-field

---

similar with the --replace flag

ory patch project 650fbb1c-a376-45a2-b56c-cdf1ec2d1c74 \
	--replace '/name=NewName'

leads to

invalid argument "/name=\"NewName\"" for "--replace" flag: parse error on line 1, column 7: bare " in non-quoted-field

Relevant log output

No response

Relevant configuration

No response

Version

not sure if this makes sense here

On which operating system are you observing this issue?

Ory Cloud

In which environment are you deploying?

Ory Cloud

Additional Context

No response