Unify edit-related terminology in WebUI: use '수정'/'edit' for modifying existing values, keep '설정'/'settings' for feature configuration

[ironAiken2]

Problem

WebUI UI labels inconsistently mix 설정 / 수정 / 편집 / 업데이트 (Korean) and edit / modify / setting / update (English) for actions that change existing values.

Rule to apply

• Use Korean '수정' / English 'edit' when the action modifies values that were set at creation time — e.g., editing a resource group that was created with initial values.
• Keep Korean '설정' / English 'settings' when the action configures a feature itself — e.g., fair share settings, where the user is changing the configuration of the feature rather than editing a previously created entity.

Scope

• Audit resources/i18n/ko.json / en.json (and propagate to other languages) for labels using 설정/편집/업데이트 (modify/setting/update) where the action is actually editing initially-set values, and replace them with 수정/edit.
• Do NOT blanket-replace: feature-configuration contexts (e.g., fair share settings) must remain 설정/settings.
• Update terminology.json if needed so the terminology checker enforces this distinction going forward.

JIRA Issue: FR-3331