Support deployment of RFDETRKeypointPreview weights

[sergii-bond]

What does this PR do?

Adds support to make this work:

deploy_model = RFDETRKeypointPreview.from_checkpoint(DEPLOY_CHECKPOINT_PATH)
deploy_model.deploy_to_roboflow(...)

Type of Change

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

Testing

• I have tested this change locally
• I have added/updated tests for this change

Test details:

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in hard-to-understand areas
• My changes generate no new warnings or errors
• I have updated the documentation accordingly (if applicable)

Additional Context

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	pypi/​numpy@​2.4.6 ⏵ 2.3.5

View full report

[jarbas-roboflow]

Status: ❌ Request Changes — Gist: https://gist.github.com/jarbasrf/cd3ff021bbe7076f1f49a532c64436e9. Resumo: The implementation is coherent, but it lacks a behavior-level test proving that an RF-DETR keypoint checkpoint produces a valid upload archive.

[jarbas-roboflow]

Status: ✅ Approve — Gist: https://gist.github.com/jarbasrf/d580720fed5efde64d35c0d6684adcc9. Resumo: The keypoint deployment paths are coherent and now have focused coverage for exported and raw Lightning checkpoints. No merge-blocking issue remains.

[jarbas-roboflow]

Status: ✅ Approve — Gist: https://gist.github.com/jarbasrf/57a7c83b0f08b93fb2efa372f1fedffe. Resumo: The implementation matches RF-DETR’s checkpoint and configuration contracts, with focused coverage of packaging and mismatch paths. No merge-blocking defect was found.