Require DataDesigner 0.9.0

[nabinchha]

What changed

• require DataDesigner 0.9.0 or newer in data-designer-github
• require DataDesigner 0.9.0 or newer in data-designer-retrieval-sdg
• regenerate uv.lock with data-designer, data-designer-config, and data-designer-engine at 0.9.0
• remove the no-longer-required email-validator and dnspython transitive packages from the lockfile

Why

This is a follow-up to #56. That PR upgraded the vulnerable dependency set against DataDesigner 0.8.0, but DataDesigner 0.9.0 was published after #56 merged. Requiring the new stable release keeps both affected plugins on the latest supported DataDesigner line.

DataDesigner 0.9.0 still constrains cryptography below 50 and PyArrow below 25, so the compatible security resolutions remain cryptography 49.0.0 and PyArrow 24.0.0.

Impact

Fresh installations of both plugins now resolve the DataDesigner 0.9.0 package family while retaining the security floors introduced by #56.

Validation

• uv lock --check
• make all
• 309 tests pass across devtools and all plugins
• isolated installs of both affected plugins resolve DataDesigner 0.9.0
• all four plugin entry points validate
• generated docs, catalog, package index, CODEOWNERS, and license checks pass

[shan-nvidia]

The package requirements are raised to Data Designer 0.9.0, but the checked-in catalog still advertises the old compatibility floors (data-designer>=0.5.7 for data-designer-github and data-designer>=0.8.0 for data-designer-retrieval-sdg). Could you update both catalog entries' requirement and specifier fields to >=0.9.0?

[nabinchha]

The package requirements are raised to Data Designer 0.9.0, but the checked-in catalog still advertises the old compatibility floors (data-designer>=0.5.7 for data-designer-github and data-designer>=0.8.0 for data-designer-retrieval-sdg). Could you update both catalog entries' requirement and specifier fields to >=0.9.0?

Thanks for the flag! Addressed in 88f5cf1