docs(i18n): add Italian (it) translation guidelines"

[SruthiSathya]

Why

With recent agentic evolution, integrating LLM CLIs (e.g., Claude Code, Copilot CLI, Gemini CLI) through manually rendered prompts (such as in #55917) creates maintenance overhead and tight coupling to specific tools.

Introducing a structured Agent Skills framework under .github/skills/:

• Provides a generic, tool-agnostic solution
• Reduces maintenance burden
• Improves consistency across locales
• Makes terminology rules explicit and centralized
• Enables scalable automation for future locale additions

This approach clearly separates:

• Global Airflow terminology rules
• Locale-specific translation guidelines

which improves clarity and long-term maintainability.

How

Add Airflow terminology–specific translation skills under .github/skills/translation.

For SKILL.md, we should only mention global-level Airflow terminology guidelines.

e.g., use Dag instead of DAG; some Airflow terms should remain in English, such as Dag and XCom.
Each locales/{locale-name}.md file should document locale-specific guidelines, based on the existing locale files under airflow-core/src/airflow/ui/public/i18n/locales/{locale-name}/.

.github/skills/airflow-translations
├── locales
│   ├── it.md
│   # ... all the locales we currently have, each with locale-specific skills
│   └── zh-TW.md
└── SKILL.md # global-level Airflow terminology guidelines

If your locale does not yet have ‎airflow-core/src/airflow/ui/public/i18n/locales/{locale-name}/README.md:

Please describe why we selected specific terms for the local translation in that file.

Sub-issues

• Global-level agent skills
• Locale-specific agent skills

Committer

[x] I acknowledge that I am a maintainer/committer of the Apache Airflow project.

[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

[sjyangkevin]

Thanks! Would appreciate if Italian translation owner can have a look at it when you have time. @bbovenzi, @aoelvp94 .