### Summary

When using paramiko and when doing a reboot then ansible will fail with "Failed to open session: SSH session not active". The target host is rebooted but ansible exits with error message.

Using ansible-base 2.10.4 the reboot works. Using 2.10.5rc1 or newer the reboot does not work.

Bug was caused by this PR https://github.com/ansible/ansible/pull/72688

Commenting out the lines 

        if not self._connected:
            return

from lib/ansible/plugins/connection/paramiko_ssh.py fixes the reboot.


### Issue Type

Bug Report

### Component Name

paramiko

### Ansible Version

```console (paste below)
$ ansible --version
ansible [core 2.11.0b4.post0]
  config file = /Users/kimmo/projects/ansible_bug/ansible.cfg
  configured module search path = ['/Users/kimmo/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /Users/kimmo/Library/Caches/pypoetry/virtualenvs/ansible-bug-RRBfm9wT-py3.9/lib/python3.9/site-packages/ansible
  ansible collection location = /Users/kimmo/.ansible/collections:/usr/share/ansible/collections
  executable location = /Users/kimmo/Library/Caches/pypoetry/virtualenvs/ansible-bug-RRBfm9wT-py3.9/bin/ansible
  python version = 3.9.2 (default, Mar 25 2021, 14:36:23) [Clang 12.0.0 (clang-1200.0.32.29)]
  jinja version = 2.11.3
  libyaml = True
```


### Configuration

```console (paste below)
$ ansible-config dump --only-changed
DEFAULT_HOST_LIST(/Users/kimmo/projects/ansible_bug/ansible.cfg) = ['/Users/kimmo/projects/ansible_bug/hosts.ini']
DEFAULT_REMOTE_USER(/Users/kimmo/projects/ansible_bug/ansible.cfg) = root
DEFAULT_TRANSPORT(/Users/kimmo/projects/ansible_bug/ansible.cfg) = paramiko
DEFAULT_VAULT_PASSWORD_FILE(env: ANSIBLE_VAULT_PASSWORD_FILE) = /Users/kimmo/ansible-vault.pass
DISPLAY_SKIPPED_HOSTS(env: ANSIBLE_DISPLAY_SKIPPED_HOSTS) = False
```


### OS / Environment

Target: debian 10

### Steps to Reproduce

<!--- Paste example playbooks or commands between quotes below -->
```yaml (paste below)
# Playbook:
- name: Reboot
  hosts: all
  tasks:
    - name: Reboot
      reboot:

```


### Expected Results

I expect target host to reboot and ansible to return success.

### Actual Results

Target host is rebooted but ansible reports failure.

```console (paste below)
PLAY [Reboot] **************************************************************************************************************************************************************************************************

TASK [Reboot] **************************************************************************************************************************************************************************************************
fatal: [test.example.com]: FAILED! => {"msg": "Failed to open session: SSH session not active"}

NO MORE HOSTS LEFT *********************************************************************************************************************************************************************************************

PLAY RECAP *****************************************************************************************************************************************************************************************************
test.example.com         : ok=1    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0
```

from __future__ import (absolute_import, division, print_function)
__metaclass__ = type
DOCUMENTATION = """
    author: Ansible Core Team
    name: paramiko
    short_description: Run tasks via python ssh (paramiko)
    description:
        - Use the python ssh implementation (Paramiko) to connect to targets
        - The paramiko transport is provided because many distributions, in particular EL6 and before do not support ControlPersist
          in their SSH implementations.
        - This is needed on the Ansible control machine to be reasonably efficient with connections.
          Thus paramiko is faster for most users on these platforms.
          Users with ControlPersist capability can consider using -c ssh or configuring the transport in the configuration file.
        - This plugin also borrows a lot of settings from the ssh plugin as they both cover the same protocol.