Remove binary expressions from signature files

Previously, if Metalava encountered a binary expression (e.g.
subtration) in the source definition of an annotation it would
replicate that expression in the signature file. That coupled the
signature files to the source representation, e.g. changing the
expression would would cause churn in the signature files. It also
complicated signature file parsing.

This change updates the signature files to match Metalava's new
behavior of evaluating the binary expression and just using the
resulting value.

Flag: EXEMPT mechanical refactoring does not change the API
Bug: 410756171
Test: m checkapi
Change-Id: Ifd634a7f52c1266218dc83baca36442b131bc3dd