feat(FR-2762): add deployment preset detail view in VFolderDeployModal

[agatha197]

Resolves #7122 (FR-2762)

Summary

• Add DeploymentPresetDetailModal component — read-only modal that fetches preset data via Relay and renders DeploymentPresetDetailContent inside a BAIModal
• Add DeploymentPresetDetailContent component — displays preset configuration in BAICard sections (Image, Cluster, Resources, Deployment Defaults)
• Add info button (InfoCircleOutlined) next to the preset BAISelect in VFolderDeployModal, following the VFolderSelect pattern (BAIFlex + Space.Compact); disabled when no preset is selected
• Place DeploymentPresetDetailModal as a sibling of Form (not inside Form.Item) to prevent double Relay query caused by Form.Item cloning its children on each render
• Fix rowId → id field in ServiceLauncherPageContent deployment preset query (DeploymentRevisionPreset exposes id, not rowId)
• Add modelService.DeploymentPresetDetail i18n key to all 22 locale files

[agatha197]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat(FR-2762): add deployment preset detail view in VFolderDeployModal #7127 : 3 dependent PRs (#7138 , #7192 , #7199 ) 👈 (View in Graphite)
• feat(FR-2761): add deployment preset create/edit/delete UI #7125 : 1 other dependent PR (#7129 )
• feat(FR-2750): add deployment preset management UI feature spec #7091 : 1 other dependent PR (#7165 )
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• flow:merge-queue - adds this PR to the back of the merge queue
• flow:hotfix - for urgent changes, fast-track this PR to the front of the merge queue

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has required the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Coverage report for ./react

St.❔	Category	Percentage	Covered / Total
🔴	Statements	7.96% (-0.01% 🔻)	1859/23350
🔴	Branches	7.16% (-0.01% 🔻)	1187/16578
🔴	Functions	4.71% (+0.01% 🔼)	297/6305
🔴	Lines	7.74% (-0% 🔻)	1750/22611

Show new covered files 🐣

St.❔	File	Statements	Branches	Functions	Lines
🔴	... / DeploymentPresetDetailModal.tsx	0%	0%	0%	0%

Test suite run success

865 tests passing in 40 suites.

Report generated by 🧪jest coverage report action from 4c5c5df

[agatha197]

Review Summary — FR-2762

I reviewed this PR against .specs/FR-2750-deployment-revision-preset-ui/spec.md (2차 마일스톤) and the project conventions for 'use memo', Relay/Suspense, antd v6 props, and the VFolderSelect button pattern.

What looks good

• 'use memo' directive on both DeploymentPresetDetailModal and DeploymentPresetDetailModalContent — no useMemo / useCallback introduced.
• Capability gate isSupportDeploymentPreset = baiClient.supports('deployment-preset') correctly drops the entire selector and uses fetchPolicy: 'store-only' for the list query when unsupported, avoiding a wasted network call.
• VFolderSelect pattern is mirrored: BAIFlex direction="row" gap="xs" + Space.Compact housing the ⓘ Button, disabled={!selectedPresetId} matches the spec ("선택 전 disabled").
• Read-only modal: BAIModal with footer={null}, no edit/delete buttons in the modal — matches "Modal 내 편집·삭제 버튼 없음" acceptance criterion.
• Relay query uses network-only fetch policy on detail open (correct: a fresh modal open should reflect any edits since the list was last loaded).
• All 21 locale files updated with modelService.DeploymentPresetDetail (PR description says 22; the repo has 21 — description-only nit).
• antd v6 props: BAIModal destroyOnHidden (not destroyOnClose) used correctly. No deprecated Alert.message / Steps.direction-class diagnostics introduced.

Findings addressed (1 fix)

MEDIUM — Missing error boundary around modal Suspense (react/src/components/DeploymentPresetDetailModal.tsx)

The Suspense block had no error boundary. If useLazyLoadQuery rejected (network failure, preset deleted between list-fetch and click, permission revoked, schema mismatch), the error would bubble past the modal to whatever ancestor boundary catches first — likely the page-level MainLayout boundary, taking down the entire service launcher form the user is currently filling out.

Fixed by wrapping the inner Suspense in ErrorBoundaryWithNullFallback, matching the pattern already used in AutoScalingRuleEditorModal and ModelCardDrawer. On error the modal body simply renders nothing instead of crashing the page; the user can close the modal and continue editing the form.

Commit: 4e339c7f2 fix(FR-2762): wrap preset detail modal Suspense in error boundary

Findings considered, not changed

• Space.Compact wraps a single Button. Functionally a no-op today, but matches the VFolderSelect pattern verbatim and leaves room for future siblings (refresh, edit). Kept for codebase consistency.
• Tooltip over a disabled Button — antd's pointer-events suppression on disabled buttons can swallow Tooltip hover. VFolderSelect uses the identical pattern in production (disabled={!value} + <Tooltip>); deferring any change to a project-wide convention update.
• Selector remains visible in edit mode (when endpoint exists) because it's nested under (baiClient.supports('modify-endpoint') || !endpoint). The 2차 마일스톤 spec wording targets the creation screen, but the selection isn't wired to form values yet, so this is purely cosmetic and does not affect submission.

Verification

• bash scripts/verify.sh → === ALL PASS === (Relay, Lint, Format, TypeScript)