Add database and target type support with VuMark validation

[adamtheturtle]

Summary

Implement database type and target type support to address #2962. Add DatabaseType enum (CLOUD_RECO, VUMARK) to distinguish database types and TargetType enum (IMAGE, VUMARK_TEMPLATE) for target classification. Implement InvalidTargetTypeError in VuMark generation endpoints to validate that VuMark instance generation only works on VUMARK-type databases. Update database and target serialization to include type information, and allow pre-population of VuMark targets in VuMark-type databases.

Test plan

• All existing VuMark generation tests pass (format validation, invalid accept header, invalid instance ID)
• New test added: test_non_vumark_database validates that attempting to generate VuMark instances from targets in non-VuMark databases returns InvalidTargetType error
• Database type field is properly serialized and deserialized in Flask target manager
• Target type field is properly serialized and deserialized in Flask target manager

Generated with Claude Code

---

Note

Medium Risk
Touches request routing/validation and serialization formats for databases, which can break clients if type fields or VuMark validation behavior are relied on implicitly.

Overview
Adds explicit type metadata for databases/targets and enforces VuMark-only behavior where applicable.

CloudDatabase now includes a serialized database_type_name (backed by new DatabaseType enum) and the Flask target-manager POST /cloud_databases accepts/returns it. VuMark instance generation (/targets/<id>/instances) in both the Flask and requests-mock servers now rejects non-VuMarkDatabase credentials with a new InvalidTargetType error/result code, with a new test covering this path; docs/changelog are updated accordingly.

^{Written by Cursor Bugbot for commit ce7003d. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Missing VUMARK value in DatabaseType enum

Medium Severity

The DatabaseType enum only defines CLOUD_RECO, but the PR description explicitly states it should contain both CLOUD_RECO and VUMARK. Without the VUMARK member, the database_type field on CloudDatabase can only ever be CLOUD_RECO, and any attempt to deserialize a database dict with database_type_name set to "VUMARK" (via DatabaseType[database_type_name]) would raise a KeyError.