Regenerate API signature files to correct annotation order

This does not change the API in anyway other than to enforce a
consistent, sorted order for all annotations; sorted by qualified
name of the annotation.

A simple bug in metalava meant that annotations were not sorted on an
API item that had exactly two annotations in the source. Fixing the
bug forced the regeneration of the signature files.

Bug: 143556317
Test: m checkbuild

(cherry picked from commit 7ba79915)

Change-Id: I27795de6a8c83e419cda8807b8551a13bec1db10
Merged-In: I0a3d967571bb2f796f65c96a9ce9121e3538bad9