Add errorprone check to avoid immutables Style inline + meta-annnotation

[a10y]

What happened?

We had a production issue where an immutables data object for configuration had a common style meta-annotation applied. A code-change was introduced that added a @Value.Style() annotation to expose public access to a Builder.

Because immutables does no merging of style annotations, this overrode the meta-annotation, breaking config deserialization for dozens of production deployments.

What did you want to happen?

The user should be told that this is going to produce unexpected behavior and that they should either

• Incorporate their style changes into the meta-annotation
• Inline the meta-annotations fields into the inline style declaration

[a10y]

Fixed in #1396