[Requirements] Bump storey and aiohttp to conform safety checks (mlru…

…n#1677)

requirements.txt

@@ -3,7 +3,7 @@ urllib3>=1.25.4, <1.27
 # >=3.0.2 from requests 2.25.1 <4.0 from aiohttp 3.7.3, requests is <5, so without the upbound there's a conflict
 chardet>=3.0.2, <4.0
 GitPython~=3.0
-aiohttp>=3.6,<3.8
+aiohttp~=3.8
 click~=7.0
 # kfp ~1.0.1 resolves to 1.0.4, which has google-auth>=1.6.1 which resolves to 2.x which is incompatible with
 # google-cloud-storage (from kfp) that is >=1.13.0 and resolves to 1.42.0) and has google-api-core that is
@@ -62,8 +62,7 @@ fsspec~=2021.8.1
 v3iofs~=0.1.7
 # 3.4 and above failed builidng in some images - see https://github.com/pyca/cryptography/issues/5771
 cryptography~=3.0, <3.4
-# In 0.8.12 the requirements loosen too much so pip resolver never finds a resolution
-storey~=0.10.3; python_version >= '3.7'
+storey~=0.10.4; python_version >= '3.7'
 deepdiff~=5.0
 pymysql~=1.0
 inflection~=0.5.0

tests/test_requirements.py

@@ -81,7 +81,6 @@ def test_requirement_specifiers_convention():
         "kfp": {"~=1.8.0"},
         "botocore": {">=1.20.106,<1.20.107"},
         "aiobotocore": {"~=1.4.0"},
-        "aiohttp": {">=3.6,<3.8"},
         "storey": {"~=0.8.11, <0.8.12; python_version >= '3.7'"},
         # Black is not stable yet and does not have a release that is not beta, so can't be used with ~=
         "black": {"<=19.10b0"},