fix(dr-egeria): add missing ISC Qualified Name to Link Product Dependency (ISSUE-109)

[dwolfson]

Summary

Follow-up to #376. Mandy Chessell approved that PR's Link Product Dependency template fix but asked directly whether ISC Qualified Name was still unmapped — it was, and the earlier "correctly absent, not a bug" conclusion in #376 was wrong. It was checked against a stale local .http copy (pyegeria/http clients/Egeria-api-product-manager.http, gitignored and user-managed, no drift signal). Re-checked against current upstream odpi/egeria source directly: DigitalProductDependencyProperties now extends LineageRelationshipProperties (which declares iscQualifiedName) rather than being a flat label/description-only class — a real upstream shape change the local copy predates.

• Added ISC Qualified Name (level Advanced) to the Digital Product Dependency bundle, copying the identical, pre-existing attribute definition from the Lineage Linker family (shared-attribute convention, not reinvented).
• Wired iscQualifiedName into the DigitalProductDependencyProperties body in collection_manager_processor.py.
• Regenerated templates — the field now appears in the Advanced template only, matching its declared level (correctly absent from Basic).
• Logged as ISSUE-109 in PYEGERIA_ISSUES.md, including the lesson about re-checking against raw.githubusercontent.com/odpi/egeria/main/... directly when a domain expert questions a "confirmed not a bug" conclusion, rather than re-trusting the same stale local copy.

Test plan

• New test test_link_product_dependency_sends_isc_qualified_name in tests/micro-tests/test_collection_link_multilink_guid.py
• pytest tests/micro-tests/ — full suite passes
• Verified via the Spec Editor's POST /api/validate/{family} — no structural findings
• Confirmed the two ISC Qualified Name attribute definitions (Digital Products, Lineage Linker) are byte-identical, avoiding the compact-JSON global-namespace divergence risk

🤖 Generated with Claude Code