feat(client): add positional optional to client v2 (backport #16316)

[mergify]

This is an automatic backport of pull request #16316 done by Mergify.
Cherry-pick of e078f1a has failed:

On branch mergify/bp/release/v0.50.x/pr-16316
Your branch is up to date with 'origin/release/v0.50.x'.

You are currently cherry-picking commit e078f1a49.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   api/cosmos/autocli/v1/options.pulsar.go
	modified:   client/v2/CHANGELOG.md
	modified:   client/v2/autocli/app.go
	modified:   client/v2/autocli/common_test.go
	modified:   client/v2/autocli/flag/message.go
	modified:   client/v2/autocli/flag/register.go
	modified:   client/v2/autocli/query_test.go
	modified:   client/v2/go.mod
	modified:   client/v2/go.sum
	modified:   proto/cosmos/autocli/v1/options.proto

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   simapp/go.mod
	both modified:   simapp/go.sum
	both modified:   tests/go.mod
	both modified:   tests/go.sum

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[tac0turtle]

i dont think this needs to be backported because the changes are in their own go.mods

[julienrbrt]

i dont think this needs to be backported because the changes are in their own go.mods

api changes do not but client/v2 changes still need to be backport as it imports the SDK.

[julienrbrt]

this is updated because it should point to a release branch pseudo version instead of from main.