i18n(Ko): add missing translations (Feb 11)

[1wos]

Added missing Korean Translations
Please review this translations.
/cc @choo121600 @kgw7401 @onestn @noeunkim

Before

After

---

• 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 or {issue_number}.significant.rst, in airflow-core/newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[choo121600]

Thank you for your contribution!
I have a quick question about this part.

[choo121600]

This section is currently in English. Would it be better to translate it into Korean?

I’ve also been thinking about our translation guidelines and would appreciate your thoughts on this.
So far, I’ve been transliterating terms like “triggerer” (e.g., “트리거러”) for consistency.

[onestn]

Agreed. Since prior translations already follow this approach, it makes sense to stay consistent for now until we revisit the overall convention.

@1wos Also, thanks for volunteering and contributing to the Korean translation! Much appreciated.

[1wos]

Thank you for the review and the helpful suggestion!
I've updated the translations to follow the existing transliteration convention.