Handle `Impossible to generate slot usage entry` complaints about changes in the `pattern` metadata slot

[candleindark]

Sub-issue of #389 — tracks handling Impossible to generate slot usage entry complaints about changes in the pattern metadata slot.

Remaining instance in dandischema/models.yaml on linkml-auto-converted:

• PublishedDandiset.id (parent pattern replaced with the stricter DANDI_PUBID_PATTERN).

Update:

1. The wording of the complaint is now "Cannot express in a slot_usage entry a value for the pattern" after pydantic2linkml allows partial slot_usage entry generation through Emit partial slot_usage entry with notes instead of raising pydantic2linkml#71.
2. Once Consolidate Asset/Dandiset models; gate publish validation on datePublished #419 is merged, this complaint should cease to exist in the generate models.yaml

Test plan:

• After the merge of Consolidate Asset/Dandiset models; gate publish validation on datePublished #419, ensure that there is no complaint with the text of "Cannot express in a slot_usage entry a value for the pattern" in the generated models.yaml file.

[candleindark]

This issue will be resolved once PublishedDandiset and Dandiset are consolidated into just one single class of Dandiset.