Valid command producing an error shows usage string unnecessarily when using "list environments"

[seanhamlin]

Describe the bug

Similar to #296 if you list environments for a project with zero environments, then it produces an error, and emits the help text.

Error: no environments found for project
Usage:
  lagoon list environments [flags]

Aliases:
  environments, e

Flags:
  -h, --help   help for environments

Global Flags:
      --config-file string   Path to the config file to use (must be *.yml or *.yaml)
      --debug                Enable debugging output (if supported)
  -e, --environment string   Specify an environment to use
      --force                Force yes on prompts (if supported)
  -l, --lagoon string        The Lagoon instance to interact with
      --no-header            No header on table (if supported)
      --output-csv           Output as CSV (if supported)
      --output-json          Output as JSON (if supported)
      --pretty               Make JSON pretty (if supported)
  -p, --project string       Specify a project to use
      --skip-update-check    Skip checking for updates
  -i, --ssh-key string       Specify path to a specific SSH key to use for lagoon authentication

Expected behavior

As this is a valid command, and the project is real, then it should just produce the a result set of zero results.