python3.pkgs.python-lsp-server: relax jedi dependency constraint

[tjni]

Description of changes

This will be needed so that builds continue working on staging-next after 39fc433. In particular, pyls-flake8 and python-lsp-black seem to require relaxing this so that their tests pass (for some reason).

We could also add jedi to pythonRelaxDeps but I guess my personal preference is to pull in patches when they exist on upstream. When upstream releases a version with the patch, it is easier to trace and clean up.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 23.11 Release Notes (or backporting 23.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

[tjni]

@ofborg build python310Packages.python-lsp-server python311Packages.python-lsp-server python310Packages.pyls-flake8 python311Packages.pyls-flake8 python310Packages.python-lsp-black python311Packages. python-lsp-black

[tjni]

Merging into staging-next since contributors are already finding these errors, and I'd like to make their lives easier.