### Summary

If I create a new user and install ansible with:
```
[root@awx-devel ~]# useradd tester
[root@awx-devel ~]# sudo su - tester
[tester@awx-devel ~]$ python3 -m venv ~/ansible_git_test_venv
[tester@awx-devel ~]$ source ~/ansible_git_test_venv/bin/activate
(ansible_git_test_venv) [tester@awx-devel ~]$ pip install ansible==6.0.0a1
```

And confirm I have the latest changes to the git module:
```
(ansible_git_test_venv) [tester@awx-devel ~]$ ansible-doc git | grep "Be aware that this disables a protection against MITM attacks"
        Be aware that this disables a protection against MITM attacks.
```

Then create a simple playbook like:
```
(ansible_git_test_venv) [tester@awx-devel ~]$ cat <<__EOF__ >./test.yml
> ---
> - name: Test git
>   hosts: localhost
>   connection: local
>   tasks:
>     - name: update project using git
>       git:
>         dest: "temp"
>         repo: "git@github.com:test/private_repo.git"
>         version: "HEAD"
>         force: "False"
>         accept_hostkey: True
>       register: git_result
> 
>     - debug:
>         var: git_result
> __EOF__
```

Running this playbook causes an issue:
```
(ansible_git_test_venv) [tester@awx-devel ~]$ ansible-playbook test.yml 
[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all'

PLAY [Test git] ****************************************************************************************************************************

TASK [Gathering Facts] ****************************************************************************************************************************
ok: [localhost]

TASK [update project using git] ****************************************************************************************************************************
The authenticity of host 'github.com (140.82.112.4)' can't be established.
ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? 
It's not "respecting" the accept_hostkey parameter.
```

After doing some debugging I can see that the env var is correctly being set and that moves down into the subprocess running git but I can't find any documentation that the git client actually does anything with an environment variable called GIT_SSH_OPTS.

### Issue Type

Bug Report

### Component Name

git

### Ansible Version

```console
$ ansible --version
ansible [core 2.13.0b0]
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/tester/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/tester/ansible_git_test_venv/lib64/python3.10/site-packages/ansible
  ansible collection location = /home/tester/.ansible/collections:/usr/share/ansible/collections
  executable location = /home/tester/ansible_git_test_venv/bin/ansible
  python version = 3.10.3 (main, Mar 18 2022, 00:00:00) [GCC 11.2.1 20220127 (Red Hat 11.2.1-9)]
  jinja version = 3.1.1
  libyaml = True
```


### Configuration

```console
$ ansible-config dump --only-changed
```


### OS / Environment

RHEL 8, Fedora 35

### Steps to Reproduce

<!--- Paste example playbooks or commands between quotes below -->
```yaml (paste below)

```
---
- name: Test git
  hosts: localhost
  connection: local
  tasks:
    - name: update project using git
      git:
        dest: "temp"
        repo: "git@github.com:test/private_repo.git"
        version: "HEAD"
        force: "False"
        accept_hostkey: True
      register: git_result

    - debug:
        var: git_result

### Expected Results

I expected to not get prompted on the host key.

### Actual Results

```console
TASK [update project using git] ****************************************************************************************************************************
The authenticity of host 'github.com (140.82.112.4)' can't be established.
ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? 
It's not "respecting" the accept_hostkey parameter.
```


### Code of Conduct

- [X] I agree to follow the Ansible Code of Conduct
refspec=dict(default=None),
            reference=dict(default=None),
            force=dict(default='no', type='bool'),
            depth=dict(default=None, type='int'),
            clone=dict(default='yes', type='bool'),
            update=dict(default='yes', type='bool'),
            verify_commit=dict(default='no', type='bool'),
            gpg_whitelist=dict(default=[], type='list', elements='str'),
            accept_hostkey=dict(default='no', type='bool'),
            accept_newhostkey=dict(default='no', type='bool'),
            key_file=dict(default=None, type='path', required=False),
            ssh_opts=dict(default=None, required=False),
            executable=dict(default=None, type='path'),
            bare=dict(default='no', type='bool'),
            recursive=dict(default='yes', type='bool'),
            single_branch=dict(default=False, type='bool'),
            track_submodules=dict(default='no', type='bool'),
            umask=dict(default=None, type='raw'),
            archive=dict(type='path'),
            archive_prefix=dict(),
            separate_git_dir=dict(type='path'),
        ),
        mutually_exclusive=[('separate_git_dir', 'bare'), ('accept_hostkey', 'accept_newhostkey')],
        required_by={'archive_prefix': ['archive']},
        supports_check_mode=True
    )
    dest = module.params['dest']
    repo = module.params['repo']
    version = module.params['version']
    remote = module.params['remote']