v1.0.1: fix: Prevent masking UUIDs as card numbers

UUIDs, with their hexadecimal digits and hyphens, could be mistakenly identified as
valid payment card numbers after processing (e.g., the first 13 digits might
pass Luhn and match a card scheme prefix). This led to UUIDs being masked in
logs, making records unsearchable, and triggering false positive alerts.

The sanitizer now explicitly checks if a potential card number candidate is
entirely contained within a UUID. If so, it is ignored. This ensures UUIDs are
preserved and false alarms are prevented. The parsing loop also ensures that
actual PANs next to rejected candidates are not skipped.