Add sas_data_maker_vulnerable_persons.yaml

[mccalluc]

• Replace Add sas-data-maker-vulnerable-persons Deployment #150: My sense is that a new PR is the best way to rerun tests.

[mccalluc]

@ganevgv : I added a TODO to double check the release_type, and a fixed a couple schema validation errors. The syntax can be confusing. Example:

    sources: |
      - Usecase by ICO: https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-sharing/privacy-enhancing-technologies/case-studies/synthetic-data-to-test-the-effectiveness-of-a-vulnerable-persons-detection-system-in-financial-services/
      - Usecase by Nationwide: https://medium.com/nationwide-technology/hazy-synthetic-data-to-fuel-rapid-innovation-fd24f2e21685
      - PrivBayes paper: https://dl.acm.org/doi/10.1145/3134428
      - DoppelGANger paper: https://arxiv.org/abs/1909.13403
    registry_authors:
      - Georgi Ganev

• sources is a block-quoted string with the |: downstream, it is interpreted as markdown, and we get a bullet list.
• registry_authors is required to be an array in the schema, so no |: Instead the - marks array members.

Right now, there's also a check that the slug matches the data in the record. The result can be long, but I don't think we need to revisit that design decision in this PR. Another example of a long PR is:

url_slug: korean-government-statistical-data-hub-platform-kostat-national-statistics-office-of-korea--2021

[bhaswarpurohit]

LGTM