CI: Fix jedi upgrades causes deprecation warning

[charlesdong1991]

• closes CI: seems jedi caused ci to fail in certain versions #31324
• tests added / passed
• passes black pandas
• passes git diff upstream/master -u -- "*.py" | flake8 --diff
• whatsnew entry

[alimcmaster1]

Assume the warning is raised in the Jedi code? Is there an issue open upstream - so hopefully this gets fixed?

[charlesdong1991]

emm, will take a look at jedi and see if a new issue is needed there
@alimcmaster1

- Big **Script API Changes**:
    - The line and column parameters of ``jedi.Script`` are now deprecated
    - ``completions`` deprecated, use ``complete`` instead
    - ``goto_assignments`` deprecated, use ``goto`` instead
    - ``goto_definitions`` deprecated, use ``infer`` instead
    - ``call_signatures`` deprecated, use ``get_signatures`` instead
    - ``usages`` deprecated, use ``get_references`` instead
    - ``jedi.names`` deprecated, use ``jedi.Script(...).get_names()``
- ``BaseDefinition.goto_assignments`` renamed to ``BaseDefinition.goto``

Update:
i opened an issue there, and see if can get a quick response and see where issue should be solved, maybe for now we could leave a TODO first and merge this to make CI green
davidhalter/jedi#1481

Update2:
based on explanation from jedi, seems ipython uses something which is deprecated in jedi and raises warning in the latest version, so we see a warning here.

[jreback]

thanks @charlesdong1991

can you create an issue to see what we should do once a new jedi is released (e.g. revert this patch), but maybe we do nothing.

[charlesdong1991]

based on jedi explanation, I think Ipython needs to react on the deprecation, and I will create an issue here and also in ipython later tonight.

Once ipython changes and no longer raises warning, i think we could revert the change then. @jreback