Allow co-hosted Durable Agents and Workflows without enabling HTTP triggers

Description

Durable Agents and Durable Workflows appear to run together in the same Function App only when enableHttpTrigger is explicitly set to true.

HTTP endpoints should not be required for applications that invoke agents and workflows internally or through queue, timer, or other event-driven triggers. Requiring HTTP exposure also creates an unnecessary security and configuration surface.

Expected behavior

Durable Agents and Durable Workflows should be able to coexist and run in the same Function App without exposing HTTP triggers. HTTP and status endpoints should be independently opt-in.

Acceptance criteria

• Agents and workflows can be hosted together with HTTP triggers disabled.
• Enabling an HTTP trigger is optional for each registered agent or workflow.
• Disabling HTTP triggers does not prevent internal or event-driven invocation.
• No HTTP endpoint is generated for registrations where it is disabled.
• Invalid configurations produce a clear startup or configuration error.