Add Japanese localization entries for forms and abilities from the latest games

[nikollson]

Change description

Add Japanese localization entries for Pokemon forms and abilities from the latest games.

This PR includes:

• Japanese ja / ja-hrkt form names for selected Mega and Gigantamax forms
  • Gigantamax Form / キョダイマックスのすがた
  • Mega Clefable / メガピクシー
• Japanese ability names for newer abilities
  • Supersweet Syrup / かんろなミツ
  • Mega Sol / メガソーラー
• Japanese ability flavor text entries for abilities that already have Japanese names
  • When the Pokémon takes damage from a move, it burns the attacker. / 技のダメージを受けると　相手をやけど状態にする。

The Japanese entries in this PR were checked against in-game text from Pokemon Scarlet/Violet and Pokemon Champions, as well as official Pokedex pages, for example:

• https://zukan.pokemon.co.jp/?sort_type=5

How to test:

• Run make build-db
• Run make test
• Start the local server with make serve
• Verify affected endpoints such as:
  • /api/v2/pokemon-form/<form>/
  • /api/v2/ability/<ability>/

AI coding assistance disclosure

I used AI coding assistance to help create small helper scripts for inspecting the repository data, listing Japanese localization entries that were not yet covered for newer game content.

I manually reviewed and edited the final data changes myself, then verified the results locally with:

• make build-db
• make test
• direct checks against affected API endpoints

Contributor check list

• I have written a description of the contribution and explained its motivation.
• I have written tests for my code changes (if applicable).
• I have read and understood the AI Assisted Contribution guidelines.
• I will own this change in production, and I am prepared to fix any bugs caused by my code change.

[Naramsim]

Everything seems fine apart from the comment I left. I don't know if we should only use hiragana/katakana for that language id or maybe remove the entries for the language id 1.

[Naramsim]

Hi, language 1 should be japanese hiragana/katakana only. Maybe these newer games use always kanjis?

[nikollson]

Thanks for pointing that out.

In Sword/Shield, the in-game language selection allowed two Japanese display options.

Available:

• kana-only Japanese text (ja-hrkt)
• standard Japanese text with kanji (ja)

From Scarlet/Violet onward, the in-game language selection allows only one Japanese display option.

Available:

• standard Japanese text with kanji (ja)

Not available:

• kana-only Japanese text (ja-hrkt)

Because of that, my understanding is that the Scarlet/Violet ja-hrkt entries already present in PokeAPI were normalized manually into kana-only Japanese text.

For the data added in this PR, it may be more natural to do the same and rewrite the new ja-hrkt entries manually into kana-only text. Would that be okay?

[Naramsim]

Either that or omit the data

[nikollson]

OK, I updated the PR so it no longer adds ja-hrkt(1) entries. I expect consumers of newer game data will use ja (11) instead.

[pokeapi-machine-user]

A PokeAPI/api-data refresh has started. In ~45 minutes the staging branch of PokeAPI/api-data will be pushed with the new generated data.

The staging branch will be deployed in our staging environment and the entire API will be ready to review.

A Pull Request (master<-staging) will be also created at PokeAPI/api-data and assigned to the PokeAPI Core team to be reviewed. If approved and merged new data will soon be available worldwide at pokeapi.co.

[pokeapi-machine-user]

The updater script has finished its job and has now opened a Pull Request towards PokeAPI/api-data with the updated data.

The Pull Request can be seen deployed in our staging environment when CircleCI deploy will be finished (check the start time of the last build).