### Summary

`ansible --version` puts a trailing space at the end of its first output line. The trailing space was introduced in #72287

This breaks ansible version detection in Vagrant. Though it would be possible to fix the version detection in Vagrant by trimming whitespace before comparing strings, I assume the addition of the trailing space was an accident since the PR doesn't indicate any intent to do so.

Since I already identified the lines which introduced this bug, I'll be happy to create a PR to remove the trailing space as well. Just waiting for your confirmation that this is indeed a bug to fix and not intended behavior.

### Issue Type

Bug Report

### Component Name

ansible --version

### Ansible Version

```console
$ ansible --version
ansible [core 2.11.1] 
  config file = /home/fs-dev/Development/VagrantVMs/ansible.cfg
  configured module search path = ['/home/fs-dev/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/fs-dev/.local/lib/python3.8/site-packages/ansible
  ansible collection location = /home/fs-dev/.ansible/collections:/usr/share/ansible/collections
  executable location = /home/fs-dev/.local/bin/ansible
  python version = 3.8.5 (default, May 27 2021, 13:30:53) [GCC 9.3.0]
  jinja version = 2.10.1
  libyaml = True
```


### Configuration

```console
$ ansible-config dump --only-changed
CALLBACKS_ENABLED(/home/fs-dev/Development/VagrantVMs/ansible.cfg) = ['profile_roles', 'profile_tasks', 'timer']
```


### OS / Environment

Ubuntu 20.04.2 LTS

### Steps to Reproduce

<!--- Paste example playbooks or commands between quotes below -->
```yaml (paste below)
ansible --version
```
First line of output ends on trailing space

### Expected Results

`ansible --version` should output its version without trailing space:  
`ansible [core 2.11.1]`

### Actual Results

```console
ansible [core 2.11.1] 
```


### Code of Conduct

- [X] I agree to follow the Ansible Code of Conduct
"""
    Add options for commands which can run tasks as another user
    Note that this includes the options from add_runas_prompt_options().  Only one of these
    functions should be used.
    """
    runas_group = parser.add_argument_group("Privilege Escalation Options", "control how and which user you become as on target hosts")
    
    runas_group.add_argument("-b", "--become", default=C.DEFAULT_BECOME, action="store_true", dest='become',
                             help="run operations with become (does not imply password prompting)")
    runas_group.add_argument('--become-method', dest='become_method', default=C.DEFAULT_BECOME_METHOD,
                             help='privilege escalation method to use (default=%s)' % C.DEFAULT_BECOME_METHOD +
                                  ', use `ansible-doc -t become -l` to list valid choices.')
    runas_group.add_argument('--become-user', default=None, dest='become_user', type=str,
                             help='run operations as this user (default=%s)' % C.DEFAULT_BECOME_USER)
    add_runas_prompt_options(parser, runas_group=runas_group)
def add_runas_prompt_options(parser, runas_group=None):
    """
    Add options for commands which need to prompt for privilege escalation credentials
    Note that add_runas_options() includes these options already.  Only one of the two functions
    should be used.
    """
    if runas_group is None:
        runas_group = parser.add_argument_group("Privilege Escalation Options",
                                                "control how and which user you become as on target hosts")
    runas_group.add_argument('-K', '--ask-become-pass', dest='become_ask_pass', action='store_true',
                             default=C.DEFAULT_BECOME_ASK_PASS,
                             help='ask for privilege escalation password')
    parser.add_argument_group(runas_group)
def add_runtask_options(parser):