Fix scraping multiple URLs

[WithoutPants]

The mapped scraper functionality is in sore need of a rework. #5294 has highlighted this with the new URLs field. For now, I've hacked in a solution that should correctly convert URLs to a list.

Notably, this does not work where URLs is used in a sub-object scenario. For example, it will populate only a single URL in the URLs field of performers within a scene scrape. This is because there is currently no way to determine which performer a given URL value belongs to. Therefore, it follows existing convention and assigns one URL for each performer result. This means that it is not possible to have multiple URLs for any performer within a scene scrape.

Resolves #5294

For testing, I used the following performer scraper for LinkTree:

name: LinkTree
performerByURL:
  - action: scrapeXPath
    url:
      - linktr.ee
    scraper: performerScraper

xPathScrapers:
  performerScraper:
    performer:
      Name: //div[@id='profile-title']/h1/text()
      URLs:
        selector: //div[@id='links-container']//a/@href

[DogmaDragon]

Tested with several existing community scrapers (IAFD, The Nude, Babepedia, MFC) and some custom scrapers.
Tested across different actions (script, scrapeJson, scrapeXPath).

Everything looks to work in my testing so far.

If URLs is used, URL, Twitter and Instagram are ignored while URLs is processed correctly. Which maintains compatibility for older scrapers.