REFACTOR-#7105: Deprecate 'cfg.RangePartitioningGroupby'

[dchigarev]

What do these changes do?

Deprecate cfg.RangePartitioningGroupby in favor of cfg.RangePartitioning

• 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 Recommend using cfg.RangePartitioning instead of cfg.RangePartitioningGroupby in docs #7105
• tests added and passing
• module layout described at docs/development/architecture.rst is up-to-date

[dchigarev]

the technique of making RangePartitioning and RangePartitioningGroupby siblings (as we did it before with ExperimentalGroupbyImpl) won't work here, since we don't want for them to actually share the same value (if they would be siblings, RangePartitioningGroupby.put(True) would enable other range-part implementations, not only groupby) that's why introducing this hacky helper function for now

[anmyachev]

LGTM!

[anmyachev]

@dchigarev should we merge the PR before the next release or after?

[dchigarev]

I think we should merge it before release cc @YarShev ?