feat: MetaFieldRanker update

[sjrl]

Related Issues

• partially addresses the RecentnessRanker in issue Port selected 1.x components to 2.x #6673. Only partially because this does not introduce the infer_type boolean discussed with @masci that would toggle whether we try to auto detect the type of the specified meta_field if all values of that meta field value are strings. Instead in this PR we focused on robustness of the MetaFieldRanker to fail less often by handling more edge cases and writing appropriate warning messages for them.

Proposed Changes:

• Makes the MetaFieldRanker more robust. Specifically to prevent the ranker from throwing an error if one or more of the documents doesn't contain the specific meta data field. Now those documents will be ignored for ranking purposes and placed at the end of the ranked list so we don't completely throw them away.
• Adding a sort_order that can have values of descending or ascending. This allows the user to decide which direction to sort the meta values. Before we had descending hard-coded. ascending could be useful, for example, ranking golfers were the the lowest score is best.
• Refactoring
  • Used logger.warning where appropriate
  • consolidated duplicate code
  • added more params to the run time so users have more flexibility

How did you test it?

• updated and added unit tests
• removed integration markings since all tests run very fast

Notes for the reviewer

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[coveralls]

Pull Request Test Coverage Report for Build 7534119821

Warning: This coverage report may be inaccurate.

We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.7%) to 87.891%

---

Totals
Change from base Build 7529773910:	0.7%
Covered Lines:	4355
Relevant Lines:	4955

---

💛 - Coveralls

[anakin87]

Looks very good to me!

I left only a small comment to improve the expressiveness of the release note.