Minor issues about verbose option

**Describe the bug**

Verbose option is not accurate

**To Reproduce**

If you go in mbed-os-example-blinky

````
$ mbedtools compile -m NUCLEO_G031K8 -t ARM
xxxx

More information may be available by using the command line option '-v'.
````

As indicated in the console, I tried the command line option '-v':
````
$ mbedtools compile -m NUCLEO_G031K8 -t ARM -v
Usage: mbedtools compile [OPTIONS]
Try 'mbedtools compile -h' for help.

Error: no such option: -v
````
=> issue 1 ?

I changed the placement:
````
$ mbedtools -v compile -m NUCLEO_G031K8 -t ARM
xxx
More information may be available by using the command line option '-vv'.
````
=> exactly the same console print as without '-v'...
=> issue 2 ?

````
$ mbedtools -vv compile -m NUCLEO_G031K8 -t ARM
xxx
More information may be available by using the command line option '-vvv'.
````
=> exactly the same console print as with or without '-v'...

````
$ mbedtools -vvv compile -m NUCLEO_G031K8 -t ARM
xxx
More information may be available by using the command line option '--traceback'.
````
=> now we have more prints :-)

**Desktop (please complete the following information):**
- OS: Windows
- Version: 10

**Mbed (please complete the following information):**
- Device: NA
- Mbed OS Version: 6.9.0
- Mbed CLI 2 Version: 7.7.0

**Additional context**
Add any other context about the problem here.

Start by running the reported mbedtools compile commands on Windows and inspect how the global -v, -vv, -vvv, and --traceback options are registered and passed to compile. Done means the documented option placement is accepted, each verbosity level changes the output as intended, and the follow-up message accurately names the next option.

Written by the indexing model from the issue text.