feat(node-type-registry): mark all task-identifier fields as function-ref

[pyramation]

Summary

Only 3 of the ~11 task-identifier fields in the node-type registry carried format: 'function-ref' (JobTrigger.task_identifier, SearchVector.job_task_name + its nested chunking_task_name). This annotates the rest so a schema-driven UI can render a function picker uniformly (groundwork for the Triggers/Source UI plan, constructive-planning#1559):

• ProcessExtraction.task_identifier
• ProcessFileEmbedding.task_identifier + nested chunks.chunking_task_name
• ProcessImageEmbedding.task_identifier + nested chunks.chunking_task_name
• ProcessImageVersions.task_identifier
• ProcessChunks.chunking_task_name
• SearchUnified nested vector.chunks.chunking_task_name

Purely annotative — no generator behavior reads format. blueprint-types.generated.ts untouched: regenerating it produced only section reordering (its committed order is stale relative to src/), and format annotations don't affect the emitted TS types.

Mirrored in constructive-io/constructive-db (same source files, plus its regenerated SQL seed/fixture/bundle).

Link to Devin session: https://app.devin.ai/sessions/a57b6055309d4a50a24aaeee9c3b2399
Requested by: @pyramation

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring