Add 2025_daSilva_NeolithicHLA

[TCLamnidis]

Adds/Updates 2025_daSilva_NeolithicHLA

Linked to poseidon-framework/minotaur-recipes#192

If this PR adds a new package to the archive, please note:
New packages added to the minotaur archive are always published in version 1.0.0.
This means that any and all changes made to the package during the review process, should only bump the Minor or Patch version of the package.

PR checklist:

• The package description has been updated to the title of the paper.
• This package contains a BibTex file.
• The month field in the BibTex file is formatted as a three letter code.
• If this package already exists in the community archive:
  • The information from the community archive was used to fill-in empty janno fields (if applicable).
  • The commands used for the fill-in and any tool versions are kept track of in the README file.
  • The BibTex key used for the citation is identical to that in the corresponding package in the community archive.
  • The DOI in the BibTex file is identical to the one used in the corresponding package in the community archive.
• If the janno information was collected manually:
  • Add any additional contributors to POSEIDON.yml
• Any scripts/commands used to prepare the pacakge are kept track of in the README file.
• Country information is also present in the Country_ISO column.
• Any columns in the janno that are entirely missing or n/a should be removed from the janno.
• If Y_Haplogroups were provided in the ISOGG format, the column should be renamed to Y_Haplogroups_ISOGG
• Poseidon_IDs in the Relation_To column contain the _MNT suffix.

Once the Pull Request has passed the review process, ensure the package version is bumped once more before publishing with:

trident rectify -d <package_dir> --logText 'Bump version for release' --packageVersion Major --checksumAll

[TCLamnidis]

@SandraPenske, could you have a look at the package that resulted from your recipe request?
Does the janno look alright to you?
Asking because the janno you provided included meta-information for more IDs than were associated with the publication in the ENA, and hence the SSF file and the package.

[TCLamnidis]

@SandraPenske confirmed that everything looks fine, so this can be merged.