GRAPHQL Paradox Pokemon Have Duplicate Ability entries with one being described as a hidden one

Steps to Reproduce:

Using this query:
query MyQuery { pokemon_v2_ability(where: {id: {_eq: 282}}) { id name pokemon_v2_pokemonabilities{ is_hidden pokemon_v2_pokemon { id name pokemon_species_id types: pokemon_v2_pokemontypes { pokemon_v2_type { name id } } } } } } .
Gives a response from the https://beta.pokeapi.co/graphql/v1beta endpoint with duplicate entries for each pokemon where it's the same ability but one is described as being it's hidden one:
{ "data": { "pokemon_v2_ability": [ { "id": 282, "name": "quark-drive", "pokemon_v2_pokemonabilities": [ { "is_hidden": false, "pokemon_v2_pokemon": { "id": 990, "name": "iron-treads", "pokemon_species_id": 990, "types": [ { "pokemon_v2_type": { "name": "ground", "id": 5 } }, { "pokemon_v2_type": { "name": "steel", "id": 9 } } ] } }, { "is_hidden": true, "pokemon_v2_pokemon": { "id": 990, "name": "iron-treads", "pokemon_species_id": 990, "types": [ { "pokemon_v2_type": { "name": "ground", "id": 5 } }, { "pokemon_v2_type": { "name": "steel", "id": 9 } } ] } },...

Run the supplied query against the https://beta.pokeapi.co/graphql/v1beta endpoint and compare the returned pokemon_v2_pokemonabilities entries for ability 282. Trace the source data or GraphQL relationship responsible for the duplicate Quark Drive records; done means each affected Pokémon no longer has the same ability represented twice with conflicting is_hidden values.