Bump jaydebeapi and jpype1

[hithwen]

TL;DR: We're performing a patch on jaydebeapi that has been solved in newer versions. However the new version has different requirements on py2 and py3

Related to: baztian/jaydebeapi#117

Original patches:

• Patch jaydebeapy datadog-agent#4425
• Fix jpype patch datadog-agent#4577

Omnibus change: DataDog/datadog-agent#5830

Pinning jpype1==0.7.1 causes this error on py3:

E       import jpype
E     File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/jpype/__init__.py", line 17, in <module>
E       import _jpype
E   ImportError: numpy.core.multiarray failed to import

Options are to pin jpype1 in py2 and py3 differently or pin numpy>=1.16.0 as well

[AlexandreYang]

I guess the next step is to remove the patch from datadog-agent repo. Could you link that PR once created ?

[codecov]

Codecov Report

Merging #6963 into master will increase coverage by 2.64%.
The diff coverage is n/a.

Impacted Files	Coverage Δ
oracle/tests/conftest.py	60.71% <ø> (ø)
amazon_msk/tests/conftest.py
rethinkdb/tests/unit/test_config.py
system_swap/tests/conftest.py
...adog_checks/cloud_foundry_api/cloud_foundry_api.py
envoy/datadog_checks/envoy/metrics.py
ceph/tests/conftest.py
dns_check/tests/mocks.py
ecs_fargate/datadog_checks/ecs_fargate/__init__.py
proxysql/datadog_checks/proxysql/proxysql.py
... and 776 more

[hithwen]

on py3 jaydebeapi will bring latest jpype: https://github.com/baztian/jaydebeapi/blob/master/setup.py#L23

[AlexandreYang]

Shall we raise an issue on jaydebeapi repo about that ?

[stale]

This pull request has been automatically marked as stale because it has not had activity in the last 30 days. Note that this will not be automatically closed, but the notification will remind us to investigate why there's been inactivity.

addressed

[hithwen]

getting an error on py3, but it works locally:

py38-12.2-jdbc run-test: commands[1] | pytest -v
ImportError while loading conftest '/home/vsts/work/1/s/oracle/tests/conftest.py'.
tests/conftest.py:8: in <module>
    from datadog_checks.oracle import Oracle
datadog_checks/oracle/__init__.py:6: in <module>
    from .oracle import Oracle
datadog_checks/oracle/oracle.py:16: in <module>
    import jpype
.tox/py38/lib/python3.8/site-packages/jpype/__init__.py:20: in <module>
    from ._core import *
.tox/py38/lib/python3.8/site-packages/jpype/_core.py:20: in <module>
    from . import types as _jtypes
.tox/py38/lib/python3.8/site-packages/jpype/types.py:38: in <module>
    from ._jarray import *
.tox/py38/lib/python3.8/site-packages/jpype/_jarray.py:213: in <module>
    _jcustomizer._applyCustomizerPost(_jpype._JArray, _JArrayProto)
.tox/py38/lib/python3.8/site-packages/jpype/_jcustomizer.py:166: in _applyCustomizerPost
    _applyCustomizerImpl(cls.__dict__, proto, sticky,
.tox/py38/lib/python3.8/site-packages/jpype/_jcustomizer.py:148: in _applyCustomizerImpl
    setter(p, v)
.tox/py38/lib/python3.8/site-packages/jpype/_jcustomizer.py:167: in <lambda>
    lambda p, v: type.__setattr__(cls, p, v))
E   TypeError: can't apply this __setattr__ to _jpype._JClass object

In https://stackoverflow.com/questions/62908416/error-importing-jpype-cant-apply-this-setattr-to-jpype-jclass-object
it says

This is an issue with Python 3.8.4. Refer to this mailchain. Try downgrading to Python 3.8.3 in the meantime.

Locally I have 3.8.1