Update apache-libcloud requirement from <3,>=2.2.1 to >=2.2.1,<4

[dependabot]

Updates the requirements on apache-libcloud to permit the latest version.

Changelog

Sourced from apache-libcloud's changelog.

Changes in Apache Libcloud 3.3.1

Compute

- [EC2] Fix a regression introduced in v3.3.0 which would break EC2 driver for
  some regions because the driver would incorrectly try to use signature version
  2 for all the regions whereas some newer regions require signature version 4
  to be used.
If you are unable to upgrade, you can use the following workaround, as long
as you only use code which supports / works with authentication signature
algorithm version 4:
.. sourcecode:: python
import libcloud.common.aws
libcloud.common.aws.DEFAULT_SIGNATURE_VERSION = "4"
Instantiate affected driver here...

Reported by @​olegrtecno.
(GITHUB-1545, GITHUB-1546)

[EC2] Allow user to override which signature algorithm version is used for
authentication by passing signature_version keyword argument to the EC2
driver constructor.
(GITHUB-1546)

Storage

• [Google Cloud Storage] Fix a bug and make sure we also correctly handle scenario in get_object() method when the object size is returned in x-goog-stored-content-length and not content-length header.

  Reported by Veith Röthlingshöfer - @​RunOrVeith. (GITHUB-1544, GITHUB-1547)

• [Google Cloud Storage] Update get_object() method and ensure object.size attribute is an integer and not a string. This way it's consistent with list_objects() method. (GITHUB-1547)

Changes in Apache Libcloud 3.3.0

Common

</tr></table> 

... (truncated)

Commits

• 449b315 Prepare changes for v3.3.1 release.
• ec3db4a Merge pull request #1547 from Kami/google_storage_object_size_fix
• 8760e5e Merge branch 'trunk' into google_storage_object_size_fix
• dcc9389 Merge pull request #1546 from apache/ec2_regression_signature_version_fix
• af89afc Add more assertions.
• ba81fa7 Fix lint.
• 19ea61f Fix lint.
• 5557299 Add changelog entry.
• ab891db Fix a bug reported in #1544.
• f8f2f8f Add changelog entry.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)