docs: logits -> probs in Accuracy metric documentation

[Kulikovpavel]

What does this PR do?

Documentation fix for Accuracy metric

There should be probs instead of logits as input.

Before submitting

• Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure your PR does only one thing, instead of bundling different changes together?
• Did you make sure to update the documentation with your changes [if needed]?
• Did you write any new necessary tests [no need for typos, docs]?
• Did you verify new and existing tests pass locally with your changes?
• If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

• Is this pull request ready for review? (if not, please submit in draft mode)
• Check that all items from Before submitting are resolved
• Make sure the title is self-explanatory and the description concisely explains the PR
• Add labels and milestones (and optionally projects) to the PR so it can be classified
• Check that target branch and milestone are aligned!

Did you have fun?

Make sure you had fun coding 🙃

[Borda]

@Kulikovpavel pls return the checklist to the PR description, it is there on purpose...

[codecov]

Codecov Report

Merging #5340 (4d6997a) into master (0e593fb) will decrease coverage by 0%.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #5340   +/-   ##
======================================
- Coverage      93%     93%   -0%     
======================================
  Files         134     134           
  Lines        9950    9950           
======================================
- Hits         9261    9254    -7     
- Misses        689     696    +7