Wrong dependency order when listing fields as removed

[adamgundry]

When reporting incomplete migration changelogs, per #40 we list missing changes in dependency order so they can be copied directly into the changelog. However, when a field and its type is removed, the dependency order needs to be reversed, otherwise the type is listed as removed before the field.

This is hardly vital, but I thought I should record it for the next time we work on the presentation of changes.

[cdornan]

@adamgundry 👍 Agreed on all points.

Getting the reports lined up with the change logs isn't vital but it makes api-tools a delight to work with — I hardly ever have to make any changes to those reports now.