feat: adopt scope:fn naming convention for job task identifiers

[pyramation]

Summary

Establishes a scope:function_name naming convention for all job task identifiers, enabling per-scope Knative service routing and independent autoscaling.

Changes

Node-type-registry defaults — all blueprint node defaults now use scoped identifiers:

• process_file_embedding → embed:process_file_embedding
• process_image_embedding → embed:process_image_embedding
• generate_embedding → embed:generate_embedding
• generate_chunks → chunk:generate_chunks

Scope-aware routing (job-utils + knative-job-worker):

• Added parseScopedIdentifier() and getJobGatewayScopeUrls() to job-utils
• Worker routing now: (1) exact dev map match → (2) scope-based routing via INTERNAL_GATEWAY_SCOPE_URLS → (3) gateway fallback
• Legacy unscoped identifiers continue to work (backward compatible)

knative-job-service: Added scoped aliases (email:send_email_link, email:simple_email) in the function registry, pointing to the same implementations.

Docker compose: Updated JOBS_SUPPORTED and INTERNAL_GATEWAY_DEVELOPMENT_MAP with both scoped and legacy identifiers. Added INTERNAL_GATEWAY_SCOPE_URLS for per-scope service routing.

Documentation: Added Section 5 "Task Identifier Naming Convention" to jobs/README.md with the full identifier table, routing priority, and env var reference.

Convention

<scope>:<function_name>

• scope = capability domain (email, embed, chunk, extract, sms)
• function_name = specific operation in snake_case
• Each scope maps to an independent Knative service with its own scaling/resource profile

Review & Testing Checklist for Human

• Verify the scope:fn convention makes sense for your deployment topology — each scope becomes an independently scalable Knative service
• Check that legacy send-email-link / simple-email identifiers still route correctly via the dev map fallback
• Review INTERNAL_GATEWAY_SCOPE_URLS env var pattern — this is the new production routing mechanism

Notes

• Existing SQL callers in constructive-db (e.g. add_job('send-email-link', ...)) are unchanged — they'll need a follow-up PR in that repo to adopt scoped names
• Blueprint defaults only affect NEW blueprints; existing provisioned blueprints retain their stored task identifiers
• A companion function registry file will be added to constructive-db as the source-of-truth for all job-queued functions

Link to Devin session: https://app.devin.ai/sessions/0bebbaeb3b374fd28f5ed051354b3b94
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 and CI monitoring