Handle blueprints with mutliple modalities in Document Data Extration module

[doshitan]

Context

Currently all custom blueprints files are loaded as DOCUMENT type/modality. This is because the DDE module focuses in "documents" (it's in the name). But there may be situations where an IMAGE type might may sense.

Instructions

Spec out:

• If multiple modalities (likely specifically IMAGE) would be something valuable to support in the DDE module.
• How to structure support
  • Note blueprint names need to be unique, so either embed the modality into the blueprint name, or have some validation that ensures no two blueprints with different modalities share the same name (or some other workaround).

Success criteria

• A tech spec detailing approach for multiple modalities
• Potentially updated project documentation with relevant rationale if deciding not to support multiple modalities

References

Reference existing patterns, documentation, and code