FIX-#5171: Allow xgboost >= 1.7.0.

[mvashishtha]

Signed-off-by: mvashishtha mahesh@ponder.io

What do these changes do?

• first commit message and PR title follow format outlined here

  NOTE: If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

• passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
• passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
• signed commit with git commit -s
• Resolves TEST: CI: test_xgboost 1.7 on test-ubuntu[ray] is getting stuck #5171
• tests added and passing
• module layout described at docs/development/architecture.rst is up-to-date

[anmyachev]

@vnlitvinov should we add the same pins for xgboost in env_hdk.yml?

[vnlitvinov]

I have no idea as I don't have anything to do with HDK anymore, but I would like to have our requirements be as consistent as possible.

[mvashishtha]

I added the same requirement for hdk

[vnlitvinov]

@mvashishtha let's fix all .yml and .txt files, I think env_hdk.yml (and maybe requirements-doc.txt, not sure about that tho as it doesn't pin any version in it) is still missing.

[mvashishtha]

@vnlitvinov I've added env_hdk and requirements-doc pins even though those don't pin xgboost already. Also we seem to support xgboost on ray only and it's not clear to me that hdk even uses xgboost. Anyway, everything that requires xgboost now specifies the same versions.

[anmyachev]

@vnlitvinov up to you