##### SUMMARY
The file contents that end up as the output of ecs_certificates "full_chain_path" are not a valid format for import into, for example, a PKCS12 store.

This is the result of the return value of the ECS API being an array, and not properly turning that array into concatenated certificates for the resulting PEM file.

##### ISSUE TYPE
- Bug Report

##### COMPONENT NAME
ecs_certificate

##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
Applies to ansible 2.9.0.dev0

##### CONFIGURATION
N/A affects all configurations

##### OS / ENVIRONMENT
N/A affects all OS/environment


##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
Populate full_chain_path and inspect output

##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
A properly formatted PEM certificate chain

##### ACTUAL RESULTS
A certificate chain in format ['CERT','CERT']

- The organization "O=" field from the CSR will not be used. It will be replaced in the issued certificate by I(org) if present, and if not present,
              the organization tied to I(client_id).
        type: str
    tracking_id:
        description:
            - Tracking ID of certificate to reissue or renew.
            - I(tracking_id) is invalid if C(request_type=new) or C(request_type=validate_only).
            - If there is a certificate present in I(path) and it is an ECS certificate, I(tracking_id) will be ignored.
            - If there is not a certificate present in I(path) or there is but it is from another provider, the certificate represented by I(tracking_id) will
              be renewed or reissued and saved to I(path).
            - If there is not a certificate present in I(path) and the I(force) and I(remaining_days) parameters do not indicate a new certificate is needed,
              the certificate referenced by I(tracking_id) certificate will be saved to I(path).
            - This can be used when a known certificate is not currently present on a server, but you want to renew or reissue it to be managed by an ansible
              playbook. For example, if you specify C(request_type=renew), I(tracking_id) of an issued certificate, and I(path) to a file that does not exist,
              the first run of a task will download the certificate specified by I(tracking_id) (assuming it is still valid), and future runs of the task will
              (if applicable - see I(force) and I(remaining_days)) renew the certificate now present in I(path).
        type: int
    remaining_days:
        description:
            - The number of days the certificate must have left being valid. If C(cert_days < remaining_days) then a new certificate will be
              obtained using I(request_type).
            - If C(request_type=renew), a renew will fail if the certificate being renewed has been issued within the past 30 days, so do not set a
              I(remaining_days) value that is within 30 days of the full lifetime of the certificate being acted upon. (e.g. if you are requesting Certificates
              with a 90 day lifetime, do not set remaining_days to a value C(60) or higher).
            - The I(force) option may be used to ensure that a new certificate is always obtained.
        type: int
        default: 30
    request_type:
        description:
            - Operation performed if I(tracking_id) references a valid certificate to reissue, or there is already a certificate present in I(path) but either