<!--- 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
Improve route53 module performance when ZoneID is know

##### ISSUE TYPE
- Bug Report

##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
route53

##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.8.3
  config file = /home/bruno/.ansible.cfg
  configured module search path = [u'/home/user/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python2.7/dist-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 2.7.15+ (default, Nov 27 2018, 23:36:35) [GCC 7.3.0]
```

##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->

##### 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 -->
* Define a long list of DNS records
* Use a `loop` with `route53` module to update them

<!--- Paste example playbooks or commands between quotes below -->
```yaml
route53:
  state: present
  zone: example.com  # should not be required when hosted_zone_id is present
  private_zone: true  # should not be needed when hosted_zone_id is present
  hosted_zone_id: "XXXXXXXXXXX"
  record: "{{ item.name }}"
  ttl: "{{ item.ttl }}"
  type: "{{ item.type }}"
  value: "{{ item.value }}"
  overwrite: true
with_items: "{{ dns_records }}"
```

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

##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
Since hosted_zone_id is provided, this should be a simple request to Route53 API

##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
Currently the code in [route53.py](https://github.com/ansible/ansible/blob/41235ac05a7a52f102422da17d40b5952e722095/lib/ansible/modules/cloud/amazon/route53.py#L567) do a zone lookup witch may lead to a full listing with (possibly) pagination by boto.
This lookup returns a `zone` reference but only it's `id` attribute is read.
So, since the hosted_zone_id is the same id obtained above, and is developer responsibility to ensure it's correct, this lookup should be ignored and the provided hosted_zone_id used in place.

<!--- Paste verbatim command output between quotes -->

ttl:
      description: resource record cache TTL
      returned: always
      type: str
      sample: '3600'
    type:
      description: record set type
      returned: always
      type: str
      sample: A
    value:
      description: value
      returned: always
      type: str
      sample: 52.43.18.27
    values:
      description: values
      returned: always
      type: list
      sample:
      - 52.43.18.27
    weight:
      description: weight of the record
      returned: always
      type: str
      sample: '3'
    zone:
      description: zone this record set belongs to
      returned: always
      type: str