TheNude: convert to Python scraper, add scene/gallery search

[FlashSpazzbo]

Converts TheNude from YAML-only to a YAML+Python scraper. Adds scene and gallery search via the magnifying glass / "Scrape with..." UIs.

Scraper type(s)

• performerByName
• performerByURL
• sceneByName
• sceneByQueryFragment
• galleryByFragment

Changes

Performer scraping (Python)

• URLs normalized to canonical /_NNNNN.htm form, eliminating the space-in-URL problem
• Performer's own name filtered out of aliases
• Birthdate refuses month-only values rather than silently defaulting to the 1st (would produce wrong data overwriting good data)
• Career length formatted as "YYYY - YYYY" with spaces to match StashDB
• fake_tits returns "Fake" as-is (was being mapped to "Augmented" but "Fake" is the actual Stash internal value)
• Tattoos/piercings dropped — TheNude consistently reports "None" for performers known to have body art

Scene/gallery search (new)

• sceneByName + sceneByQueryFragment enables the magnifying glass search picker on scenes. Some studios provide both portrait and landscape versions of the same shoot, which TheNude lists as separate URLs; the picker lets the user choose which one
• galleryByFragment enables "Scrape with..." on galleries

Preserved from upstream

• XPath-based sceneByURL, galleryByURL, imageByURL handlers

Test cases

• Performer by URL: https://www.thenude.com/_28377.htm (Carly Lauren)
• Performer by name: "Carly Lauren"
• Scene magnifying glass: search "Naked Forest Nymph Shoot" (returns 2 results — landscape + portrait covers — for picker)
• Gallery scrape: "Nude On The Veranda"

[feederbox826]

I'm not seeing a good reason to convert to python, what can't be done in yml?

[FlashSpazzbo]

I'm not seeing a good reason to convert to python, what can't be done in yml?

Birthdate handling.

Test case: Carli Banks (https://www.thenude.com/_6444.htm) lists her birthdate as "November 1985" — month and year, no day. YAML's parseDate parses this and silently defaults to day 01, writing "1985-11-01" to Stash and overwriting whatever correct date may already exist on the performer record. The Python implementation checks for a parsed day and omits the birthdate field entirely if absent, preserving existing data. I don't think YAML can express "parse only if day component is present."

Happy to revert the other changes (URL normalization, career length formatting, fake_tits mapping, dropping tattoos/piercings, and the new sceneByName/sceneByQueryFragment/galleryByFragment search operations) to YAML if the birthdate handling is the only thing that justifies the Python conversion.

[feederbox826]

previous behaviour has been to force 01 date. you can also regex parse to nullify if it doesn't match

[FlashSpazzbo]

Closing — will resubmit as YAML-only.