FIX-#0000: follow up PR with fixes for #5634

[anmyachev]

What do these changes do?

#6650

• 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 #?
• tests added and passing
• module layout described at docs/development/architecture.rst is up-to-date

[anmyachev]

@YarShev

[anmyachev]

On a cluster, this may not be correct, since if all the processes of one node are busy, then the engine can start the calculation on another node, which will lead to incorrect receipt of the address.

One of the most likely solutions would be to return the entire dataframe and completely update the partition (all references to remote objects).

It may potentially be possible to use special API engines to obtain the address more efficiently. (for example, like in ray-project/ray#13630)

@YarShev thanks for the explanation and solution proposal!