DDN/Cli - Installation should prompt for the help command to see all the available commands

### Component
CLI
c/v3-cli

### What is the current behaviour?
```shell
--> Installing Hasura DDN CLI
-->
--> Selecting version...
--> Selected version: latest
-->
--> NOTE: Install a specific version of the CLI by using VERSION variable
--> curl -L https://graphql-engine-cdn.hasura.io/ddn/cli/v3/get.sh | VERSION=v1.0.0 bash
-->
--> Downloading DDN for darwin-arm64 to /tmp/cli-ddn-darwin-arm64
######################################################################## 100.0%
--> Download complete!
-->
--> Path '/usr/local/bin' requires root access to write.
--> This script will attempt to execute the move command with sudo.
--> Are you ok with that? (y/N)
-->
--> Moving cli from /tmp/cli-ddn-darwin-arm64 to /usr/local/bin
Password:
-->
--> DDN cli installed to /usr/local/bin
-->
3:30PM INF Checking for update...
3:30PM INF ddn cli is up to date version={"CLI":"v1.0.0","CLISemver":"1.0.0"}
DDN CLI Version: v1.0.0
```
The result of the CLI installation. It is not clear the command is
ddn, or ddn-cli or something else

### What is the expected behaviour?
Expected behaviour is help command or sample command
i.e.
```shell
run `ddn -h` to list all the commands
ddn -version to see the current version of the DDN CLI
```

### How to reproduce the issue?

1.
2.
3.

### Screenshots or Screencast

### Please provide any traces or logs that could help here.

### Any possible solutions/workarounds you're aware of?

### Keywords

Start by locating the DDN CLI installation flow and the post-install output shown in this issue. Update that output to identify the `ddn` command and show the help and version commands, then verify the messages after a CLI installation.

Written by the indexing model from the issue text.