Ensure consistent representation of field deprecated status

Previously, fields that were inherited from a hidden class into a
deprecated class were treated differently to its own fields. The former
were not marked as `@Deprecated` but the latter were. That behavior has
been corrected and this change updates the signature files accordingly.

Bug: 366411703
Test: m checkapi
Change-Id: I7d1975e73a9ede9198ba2c1a41f868c07dcf1d99