BUG: weird interaction between pyslurm, ujson that changes function signature of ujson.dumps
- [x] I have checked that this issue has not already been reported.

- [x] I have confirmed this bug exists on the latest version of pandas.

- [ ] (optional) I have confirmed this bug exists on the master branch of pandas.

---

Hi maintainers, I'd like to start with saying I'm not entirely sure if this is a `pandas` bug, but seeing that [`pandas` bundles its own `ujson`](https://github.com/pandas-dev/pandas/blob/master/pandas/_libs/src/ujson/python/version.h), figured I'd ask here.

#### Problem description
**TL;DR**: There seems to be a very strange behavior in `ujson` depending on how it is imported (in particular, depending on whether the `pyslurm` library is imported first). The observed behavior is that this modifies the function signature of `ujson.dumps` (by removing the `sort_keys` argument), as shown in the below examples. I'm not sure if this behavior is specific to importing `pyslurm` in the beginning or not, but this is just one specific example that can be used to reproduce the problem.

First, installation of these libraries via `pip` is needed:
```
pip install cython
pip install pyslurm pandas ujson
```

This is the script with the error:
```python
import pyslurm
import pandas
import ujson
print(f"pyslurm=={pyslurm.__version__}")
print(f"pandas=={pandas.__version__}")
print(f"ujson=={ujson.__version__}")
ujson.dumps({}, sort_keys=True)
```

If you run the script above, you'll see the output is:
```
pyslurm==18.08.1.1
pandas==1.0.3
ujson==2.0.3
Traceback (most recent call last):
  File "<string>", line 1, in <module>
TypeError: 'sort_keys' is an invalid keyword argument for this function
```

However, if you remove the `pyslurm` import, the problem goes away!
```py
import pandas
import ujson
print(f"pandas=={pandas.__version__}")
print(f"ujson=={ujson.__version__}")
ujson.dumps({}, sort_keys=True)
```

Also, reordering the imports somehow fixes the problem:
```py
import pandas
import ujson
import pyslurm
ujson.dumps({}, sort_keys=True)
```

#### Expected Output
Importing `pyslurm` and `pandas` shouldn't affect the behavior of my `ujson` library. Also, import orders shouldn't cause this bug.

#### Additional Info
It seems that the very specific import order that causes this is `pyslurm -> pandas -> ujson`.

I suspect this has something to do with Python's mechanism for importing C extensions, but I don't understand the internals enough to be able to debug this further.

#### Output of ``pd.show_versions()``

<details>

INSTALLED VERSIONS
------------------
commit           : None
python           : 3.8.2.final.0
python-bits      : 64
OS               : Linux
OS-release       : 4.15.0-43-generic
machine          : x86_64
processor        : x86_64
byteorder        : little
LC_ALL           : None
LANG             : en_US.UTF-8
LOCALE           : en_US.UTF-8

pandas           : 1.0.3
numpy            : 1.18.3
pytz             : 2020.1
dateutil         : 2.8.1
pip              : 20.0.2
setuptools       : 46.1.3.post20200330
Cython           : 0.29.17
pytest           : None
hypothesis       : None
sphinx           : None
blosc            : None
feather          : None
xlsxwriter       : None
lxml.etree       : None
html5lib         : None
pymysql          : None
psycopg2         : None
jinja2           : None
IPython          : None
pandas_datareader: None
bs4              : None
bottleneck       : None
fastparquet      : None
gcsfs            : None
lxml.etree       : None
matplotlib       : None
numexpr          : None
odfpy            : None
openpyxl         : None
pandas_gbq       : None
pyarrow          : None
pytables         : None
pytest           : None
pyxlsb           : None
s3fs             : None
scipy            : None
sqlalchemy       : None
tables           : None
tabulate         : None
xarray           : None
xlrd             : None
xlwt             : None
xlsxwriter       : None
numba            : None

</details>
