Contract errors and unclarity about Pokemon form names

首先，将 PokemonDetail 契约中的 held_items 和必需的 nullable 字段与 Delphox 及其他受影响 Pokémon 的响应进行比较。然后检查 aegislash、basculegion 和 basculin 的名称查找行为；当契约与实际响应一致，并且异常形态名称已记录时，即表示完成。

During testing of your OpenAI contract solution, I have come across some errors.

In the contract, it is stated this:

(Within PokemonDetail in contract)

        held_items:
          type: object              <---- held_items must be an object.
          required:
            - item
            - version_details
         

However, for example Delphox (https://pokeapi.co/api/v2/pokemon/delphox/), held_items is an empty array, which fails in parsing because it is not an object. In some cases, an attribute is required by contract but is null. These two cases produces these two errors:

com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Not a JSON Object: []
com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Not a JSON Object: null

A large number of the total pokemon in your API have one or both of these problems. (About ~100 from my incomplete testing) All my testing was done purely with methods generated from the contract with OpenAPI Generator, and when Pokemon were queried by name - not ID. I have not tested with ID query.

Also, I found out through my testing that there are a few pokemon who cannot be queried with "normal" name means. I saw in earlier issues that you are aware, but it would be helpful to have this information accessible in the PokeAPI with the actual list of Pokemon who don't fit the normal bill and need form-appendixes to their name.
For example:

• aegislash
• basculegion
• basculin