FND-3848: add pyatlan_v9 creators for the 10 Cognos asset types

[sachi-atlan]

✨ Description

Adds creator() for the 10 Cognos asset types in pyatlan_v9: CognosReport, CognosDashboard, CognosExploration, CognosFile, CognosModule, CognosPackage, CognosDataset, CognosFolder, CognosDatasource, CognosColumn. This is the exemplar connector for the Fill creator gaps in pyatlan project; later connector PRs copy its structure.

CognosReport.creator(name="Quarterly Sales", connection_qualified_name="default/cognos/1712345678", cognos_id="i1A2B3C4D5E6F")
# qualified_name == "default/cognos/1712345678/report/i1A2B3C4D5E6F"

• Exact app parity: each creator emits {connection_qualified_name}/<slug>/{cognos_id}, the string atlan-cognos-app emits today (FND-3838 census), including the dataSet2 slug for CognosDataset. A different string would re-key existing Cognos assets on every tenant.
• Shape follows the Metabase creators: Cognos qualifiedNames are flat and id-based (the parent is not part of the name), so like MetabaseDashboard the creators take no parent; the caller sets the folder / column-parent relationship. The typedef keeps the folder requiredForCreation, so validate(for_creation=True) is unchanged.
• Blank inputs raise (validate_required_fields).
• CognosColumn cognos_id is the column uuid (the value its qualifiedName is keyed on). atlan-cognos-app does not set cognosId on columns today, so on adoption columns gain a cognosId value; their qualifiedName is unchanged.
• Overlays in pyatlan_v9/model/assets/_overlays/cognos_*.py; the 10 classes are regenerated from atlanhq/models with these overlays (pkl sdkOnly=python + pre-commit, the same steps as sync-python-sdk.yaml).

Linear: FND-3848
Paired models PR: https://github.com/atlanhq/models/pull/2077 (merged); the classes here are regenerated from models master 585a201 on top of main after #1076. — adds the matching qualifiedNameFormula, which drives the regenerated _QUALIFIED_NAME_PATTERN.

---

🧩 Type of change

• 🚀 New feature (non-breaking change that adds functionality)

---

✅ How has this been tested?

• tests_v9/integration/cognos_asset_test.py (review follow-up): creates a Cognos connection and every Cognos type through its creator (folder, the 7 folder children with the folder link set by the caller, datasource, column under a dataset), retrieves each and asserts the exact qualifiedName, cognos_id, connector and parent link, then purges. Adds AtlanConnectorType.COGNOS, which Connection.creator needs.
• tests_v9/unit/model/cognos_test.py (70 tests): literal app qualifiedName per type, name pattern match, validate(), missing / blank inputs, create alias.
• Mutation check: changing the Dataset slug dataSet2 → dataset fails the parity tests.
• Generator fidelity: generating from models master with main's overlays reproduces main's Cognos classes byte-for-byte; with the models PR branch, only the 10 Cognos classes change.
• pytest tests_v9/unit: 7745 passed, 5 skipped. pre-commit clean on all changed files.
• Production parity (read-only): all 9,752 Cognos assets on a production tenant match the new _QUALIFIED_NAME_PATTERN for their type (Column 9,618 · Dataset 52 · Report 43 · Folder 22 · Datasource 6 · Package 6 · Module 5); 0 do not. So the stricter pattern rejects no existing asset.
• App vs creator: 240 records run through atlan-cognos-app's own transformers (all 10 types, every parent type, the exploration→dashboard path, ids with - _ . ~) give qualifiedNames identical to the creators.
• The 12 failing legacy tests/integration jobs also fail on every recent run of this workflow (including the sync PRs and the merged ci: ignore anyio CVE-2026-63374 for the Python 3.9 lock entry in the Trivy gate #1074); this PR touches only pyatlan_v9.

---

📋 Checklist

• My code follows the project’s style guidelines
• I’ve performed a self-review of my code
• There are no new warnings from my changes
• I’ve added tests to cover my changes
• All new and existing tests pass locally

🤖 Generated with Claude Code

[linear]

FND-3848

[Aryamanz29]

Looks good overall - two things:

• could you please resolve the merge conflicts? Looks like they're just code formatting.
• could you please also add integration tests for these creators? Assuming the typedefs are GA on the tenants, that'll confirm everything works as expected 🙏