feat(services): redesign agentic workflow configuration

[TheoGrandin74]

What changed

• rebuild the agentic workflow creation page around the agent configuration design
• add provider, MCP, skills, access, variables, network, cost, and Dockerfile configuration states
• add a rich instructions editor
• add Qovery environment and Git repository context flows
• fetch organization environments and environment services, and lock the agent to the linked environment cluster
• add editable context cards, provider settings, and Dockerfile fragments
• extend shared modal, segmented control, and Git selectors where the new flows need existing console behavior

Why

The previous creation flow did not match the new Agentic Workflows design or support the required configuration interactions.

Validation

• yarn tsc --noEmit -p libs/domains/services/feature/tsconfig.lib.json
• focused ESLint checks passed during implementation
• the new dropdown interaction spec was added, but Jest/Nx remained blocked by a stale project-graph process and was not completed before publishing

[RemiBonnet]

Qovery can create a Preview Environment for this PR.
To trigger its creation, please post a comment with one of the following command.

Command	Blueprint environment
/qovery preview cc1de7de-94e5-40f8-8e45-bc8986d9dfec	storybook
/qovery preview 964984c5-fba6-4371-88d3-a5daf99642ab	test-prod
/qovery preview 28c47145-c8e7-4b9d-8d9e-c65c95b48425	staging
/qovery preview {all|UUID1,UUID2,...}	To preview multiple environments

---

This comment has been generated from Qovery AI 🤖.
Below, a word from its wisdom :

Make it work, make it right, make it fast

[nx-cloud]

🤖 Nx Cloud AI Fix Eligible

An automatically generated fix could have helped fix failing tasks for this run, but Self-healing CI is disabled for this workspace. Visit workspace settings to enable it and get automatic fixes in future runs.

_{To disable these notifications, a workspace admin can disable them in workspace settings.}

---

View your CI Pipeline Execution ↗ for commit 51ec9f2

Command	Status	Duration	Result
nx affected --target=test --parallel=3 --config...	❌ Failed	4m 37s	View ↗
nx affected --target=lint --parallel=3	✅ Succeeded	2m 27s	View ↗
nx-cloud record -- yarn nx format:check	✅ Succeeded	7s	View ↗

💡 Dealing with memory or CPU issues? See memory and CPU details with the resource usage add-on ↗.

---

☁️ Nx Cloud last updated this comment at 2026-07-26 17:01:51 UTC