[Doc] change search ranking for partition

[DanRoscigno]

The current search results for "partition" or "fenqu" are probably not what the reader is looking for. We recommend expression partitioning, but "fenqu" leads to list partitioning. I think that the main data distribution page is the best place.

@EsoragotoSpirit can you fix the description line for the data distribution page (I put in a placeholder). Once that line is good take off the draft.

At some point I need to fix the way our crawler processes the keywords array, I only tested with single entries, which work fine, but when we add multiple keywords the ranking is not affected. I need to add some Javascript to process the array in the crawler. For now when we need multiple keywords for Pinyin I would like to test using the description field. So, for example I want the words "partition" and "bucket" in the description for data distribution, so I used the phrase "Partition and bucket data". Note that the description should be a short sentence as it appears on overview pages and in search results.

What type of PR is this:

• [ ] BugFix
• [ ] Feature
• [ ] Enhancement
• [ ] Refactor
• [ ] UT
• [x] Doc
• [ ] Tool

Does this PR entail a change in behavior?

• [ ] Yes, this PR will result in a change in behavior.
• [x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• [ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
• [ ] Parameter changes: default values, similar parameters but with different default values
• [ ] Policy changes: use new policy to replace old one, functionality automatically enabled
• [ ] Feature removed
• [ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• [ ] I have added test cases for my bug fix or my new feature
• [ ] This pr needs user documentation (for new or modified features or behaviors)
  • [ ] I have added documentation for my new feature or new function
• [ ] This is a backport pr

Bugfix cherry-pick branch check:

• [x] I have checked the version labels which the pr will be auto-backported to the target branch
  • [x] 3.3
  • [x] 3.2
  • [x] 3.1
  • [x] 3.0
  • [ ] 2.5