reproducible builds: TASTY differences

[raboof]

Similar to apache/pekko-http#566

• In pekko-connectors-google-fcm_3-1.1.0-M1-RC1.jar in org/apache/pekko/stream/connectors/google/firebase/fcm/v1/models/FcmOption (begin and and of the .tasty file)
• In pekko-connectors-huawei-push-kit_3-1.1.0-M1-RC1.jar in org/apache/pekko/stream/connectors/huawei/pushkit/models/Response (begin and and of the .tasty file)

[raboof]

OK, so interestingly FcmOption is really small, so that is a good start for a reproducer.

FcmOption has 3 @Child annotations, one for each class extending FcmOption. It seems when compiling the module after a clean, somehow references to FcmJsonSupport.scala are added to those @Child annotations in the tasty file for FcmOption (but it seems nondeterministic to which of the @Child annotations they're attached). When compiling FcmOption.scala in isolation, however (even from sbt), those references are not added at all.

Filed scala/scala3#21154

[raboof]

(looks like this missed the train for 3.3.4 but will likely be backported to LTS in 3.3.5)