i18n(ko): Improve Korean Task terminology consistency

[kddhhh23]

---

This updates mixed uses of 작업, 태스크, and untranslated Tasks in the Korean locale to consistently use 태스크 terminology wherever the original English source uses task or tasks.

• 작업 → 태스크
• Tasks → 태스크

The term 태스크 was chosen based on the reviewer discussion below.

examples showing mixed usage of '태스크', 'Tasks', and '작업'

Following the review feedback to standardize the translations, this also changes 생성하는 to 생성 중인 for consistency with other status labels.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

Requesting Korean translation review:
@choo121600 @onestn @noeunkim

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[noeunkim]

Also I'd recommend using 태스크 instead of 작업 to deliver origin meaning of the word
ref. https://www.korean.go.kr/front/imprv/refineView.do?mn_id=&imprv_refine_seq=20597

[kddhhh23]

Thank you for the suggestion! In that case, would it make sense to consistently replace existing translations of “작업” with “태스크” across all files under airflow-core/src/airflow/ui/public/i18n/locales/ko/ as well?

[choo121600]

Yes, I think that would make sense for consistency :)

[kddhhh23]

I have pushed a new commit and updated the PR description based on feedback. Please take a look when you have a moment. Thank you!

[choo121600]

LGTM, Thanks :)

[github-actions]

Hi maintainer, this PR was merged without a milestone set.
We've automatically set the milestone to Airflow 3.2.3 based on: backport label targeting v3-2-test
If this milestone is not correct, please update it to the appropriate milestone.

This comment was generated by Milestone Tag Assistant.

[github-actions]

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-2-test

You can attempt to backport this manually by running:

cherry_picker 93eee4f v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

[choo121600]

It looks like some parts are not yet present in 3-2-test. so it might make more sense to defer this to the next release instead of doing a manual backport :)