Fix incorrect PESEL checksum validation in PlPeselRecognizer

[sienioApius]

Change Description

The Polish PESEL check-digit algorithm is check = (10 - weighted_sum % 10) % 10
(see https://en.wikipedia.org/wiki/PESEL#Check_digit), but
PlPeselRecognizer.validate_result currently compares the raw
weighted_sum % 10 to the check digit, which rejects real valid PESEL numbers.

Example — 44051401458 is the canonical example used in official Polish
documentation and is algorithmically valid, but today:

>>> from presidio_analyzer.predefined_recognizers import PlPeselRecognizer
>>> PlPeselRecognizer().validate_result("44051401458")
False   # expected True

This PR:

• Corrects the check-digit formula.
• Guards against non-11-digit / non-numeric inputs (previously would raise
  IndexError on a regex-produced string shorter than 11).
• Replaces the existing test fixtures — which were generated using the buggy
  formula and would not pass real-world PESEL validators — with PESEL numbers
  that are valid under the true algorithm, plus negative cases covering wrong
  check digits, wrong length, and non-digit input.

The previous "valid" fixture 11111111114 has a real check digit of 6, not
4. The updated fixtures (44051401458, 02070803628, 11111111116) verify
against the actual PESEL standard.

Issue reference

This completes the work started in #1520 (closed on 2025-06-01 due to missing
tests). Attribution to the original author @BlaiseCz for the analysis.

Checklist

• I have reviewed the contribution guidelines
• I have signed the CLA (if required) (will sign when CLA bot prompts)
• My code includes unit tests
• All unit tests and lint checks pass locally (pytest tests/test_pl_pesel_recognizer.py → 18 passed)
• My PR contains documentation updates / additions if required

[sienioApius]

@microsoft-github-policy-service agree company="APIUS Technologies S.A."