### Summary

Writing this following #79967, which I created because I thought that I encountered a bug, but in fact I didn't know some details about how `argv` parameter works.

It would be great to have information provided to me there in the documentation in case anybody else encounter the same issues. Especially this comment was very helpful:
> precisely because you can use white space you need to separate what is not the same argument or the flag + argument are passed as a unit '--flag arg' vs '--flag' 'arg'

### Issue Type

Documentation Report

### Component Name

https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/command.py

### Ansible Version

```console
$ ansible --version
```


### Configuration

```console
# if using a version older than ansible-core 2.12 you should omit the '-t all'
$ ansible-config dump --only-changed -t all
```


### OS / Environment

Linux

### Additional Information

When the improvement is applied, it makes it more straightforward to understand how argv parameters works

### Code of Conduct

- [X] I agree to follow the Ansible Code of Conduct
- If set to C(true), append a newline to stdin data.
    version_added: "2.8"
  strip_empty_ends:
    description:
      - Strip empty lines from the end of stdout/stderr in result.
    version_added: "2.8"
    type: bool
    default: yes
notes:
    -  If you want to run a command through the shell (say you are using C(<), C(>), C(|), and so on),
       you actually want the M(ansible.builtin.shell) module instead.
       Parsing shell metacharacters can lead to unexpected commands being executed if quoting is not done correctly so it is more secure to
       use the C(command) module when possible.
    -  C(creates), C(removes), and C(chdir) can be specified after the command.
       For instance, if you only want to run a command if a certain file does not exist, use this.
    -  Check mode is supported when passing C(creates) or C(removes). If running in check mode and either of these are specified, the module will
       check for the existence of the file and report the correct changed status. If these are not supplied, the task will be skipped.
    -  The C(executable) parameter is removed since version 2.4. If you have a need for this parameter, use the M(ansible.builtin.shell) module instead.
    -  For Windows targets, use the M(ansible.windows.win_command) module instead.
    -  For rebooting systems, use the M(ansible.builtin.reboot) or M(ansible.windows.win_reboot) module.
    -  If the command returns non UTF-8 data, it must be encoded to avoid issues. This may necessitate using M(ansible.builtin.shell) so the output
       can be piped through C(base64).
seealso:
- module: ansible.builtin.raw
- module: ansible.builtin.script
- module: ansible.builtin.shell
- module: ansible.windows.win_command
author:
    - Ansible Core Team
    - Michael DeHaan