Multiple @SerializedName names choosing alternate over value.

We have run into a quirk with `@SerializedName`.

Class.java
```java
public class MyClass {
@SerializedName(value="name1",` alternate={"name2", "name3"}) String b;
}
```

Response.json
```json
{
"name1": "My Name",
"name3": "My Other Name"
}
```

In this scenario, my expectation is that GSON would choose the value `My Name` from the JSON key `name1`, because this is the expected location of the value. It seems that GSON then finds `name3` and says that is is also a valid name for `b` and overwrites the previously found value with the new one.

I'm unsure if this is due to the order of the `@SerializedName` parameters or the order of the keys in the JSON file itself.

I understand the real fix is making the endpoint returning these duplicate values at the same time, but it is surprising behavior for`@SerializedName`.