Connection to ksqlDB with cp-ksqldb-cli:7.7.0 does not work but works with ksqldb-cli:029.0

[mrt181]

Describe the bug
I am running this command to connect to my ksqldb.

> podman run --interactive --tty --rm docker.io/confluentinc/ksqldb-cli:0.29.0 \
        ksql \
        -u <username> \
        -p <password> \
        https://<my-cluster>.confluent.cloud:443

                  ===========================================
                  =       _              _ ____  ____       =
                  =      | | _____  __ _| |  _ \| __ )      =
                  =      | |/ / __|/ _` | | | | |  _ \      =
                  =      |   <\__ \ (_| | | |_| | |_) |     =
                  =      |_|\_\___/\__, |_|____/|____/      =
                  =                   |_|                   =
                  =        The Database purpose-built       =
                  =        for stream processing apps       =
                  ===========================================

Copyright 2017-2022 Confluent Inc.

CLI v0.29.0, Server v7.7.0-672 located at https://<my-cluster>.confluent.cloud

WARNING: CLI and server version don't match. This may lead to unexpected errors.
         It is recommended to use a CLI that matches the server version.

Server Status: RUNNING

Having trouble? Type 'help' (case-insensitive) for a rundown of how things work!

ksql>

All good. But when I run with a newer version I get this instead.

> podman run --interactive --tty --rm docker.io/confluentinc/cp-ksqldb-cli:7.7.0 \
        ksql \
        -u <username> \
        -p <password> \
        https://<my-cluster>.confluent.cloud:443
At most 1 arguments may be specified but 2 were found
See the -h or --help flags for usage information

Both versions have the same --help output.

To Reproduce
Steps to reproduce the behavior, include:

1. The version of KSQL -> 7.7.0.
2. connect using kdsldb-cli:0.29.0 to check that it works
3. connect using cp-ksqldb-cli:7.7.0 to check that it doesn't work

Expected behavior
The connection should work with the new version.

Actual behaviour
see bug description