<!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->

##### SUMMARY
Plugins cannot be installed using the jenkins_plugin module since upgrading to LTS 2.176.  This is due to additional CSRF security where the crumb that is issued may only be used within the same session.

In the jenkins log messages like this are reported:

```
WARNING: Found invalid crumb 5cae269d58b83057dfbd85f6c32f0845.  Will check remaining parameters for a valid one...
```

The module will then error with `Cannot install plugin.`

##### ISSUE TYPE
- Bug Report

##### COMPONENT NAME
jenkins_plugin

##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```
ansible 2.8.4
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/home/james/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.16 (default, Apr  6 2019, 01:42:57) [GCC 8.3.0]

```

##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
(no output)
```

##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->

##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
Install jenkins 2.176, attempt to install plugins using ansible, e.g. a task such as:

```
- name: "Install Jenkins plugins"
  jenkins_plugin:
    owner: jenkins  
    group: jenkins
    name: "{{ item }}"
    url: "https://{{ ansible_host }}:8090/"
    url_username: "{{ ansible_user }}"
    url_password: "{{ ansible_become_pass }}"
    force_basic_auth: yes
  with_items:
    - ansicolor
```

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

```

<!--- HINT: You can paste gist.github.com links for larger files -->

##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
The named plugin is installed in jenkins.

##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->

<!--- Paste verbatim command output between quotes -->
```paste below

```

type: bool
    default: yes
notes:
  - Plugin installation should be run under root or the same user which owns
    the plugin files on the disk. Only if the plugin is not installed yet and
    no version is specified, the API installation is performed which requires
    only the Web UI credentials.
  - It's necessary to notify the handler or call the I(service) module to
    restart the Jenkins service after a new plugin was installed.
  - Pinning works only if the plugin is installed and Jenkis service was
    successfully restarted after the plugin installation.
  - It is not possible to run the module remotely by changing the I(url)
    parameter to point to the Jenkins server. The module must be used on the
    host where Jenkins runs as it needs direct access to the plugin files.
  - "The C(params) option was removed in Ansible 2.5 due to circumventing Ansible's
    option handling"
extends_documentation_fragment:
  - url
'''
EXAMPLES = '''
- name: Install plugin
  jenkins_plugin:
    name: build-pipeline-plugin
- name: Install plugin without its dependencies
  jenkins_plugin:
    name: build-pipeline-plugin
    with_dependencies: no
- name: Make sure the plugin is always up-to-date
  jenkins_plugin:
    name: token-macro