s3token authentication not working properly

[Frode Nordahl]

Attempting to talk to swift-proxy with a S3 client, for example AWS boto3, will not work properly and you will get an error message like:

    botocore.exceptions.ClientError: An error occurred (SignatureDoesNotMatch) when calling the ListBuckets operation: The request signature we calculated does not match the signature you provided. Check your key and signing method.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/713048

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/713048
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=ed9051a9f3192f5e139062b0731de37850bacd9a
Submitter: Zuul
Branch: master

commit ed9051a9f3192f5e139062b0731de37850bacd9a
Author: Frode Nordahl <email address hidden>
Date: Fri Mar 13 19:44:14 2020 +0100

    s3token: Fix Keystone API configuration

    Upstream removed the api_version configuration option and started
    to expect the version to be encoded in the Keystone URL at Rocky.

    Add S3 API functional test.

    Remove invalid configuration items in the s3token section.

    Remove configuration templates for OpenStack versions prior to
    Mitaka.

    Change-Id: Ia3306441222f7c078d460c659701a57a5944c928
    Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/194
    Closes-Bug: #1867373