[Commonizer] Don't account for isValue when setting hasAnnotations

...of the metadata... built from the commonized Cir. With `FirElementSerializer`,
the flag is only set if there are actually some annotations, so we must
leave the metadata in the same state as they had when we accepted it as
the input.

Without this change, some test fail complaining that the commonization
result contains unexpected `true` values for `hasAnnotation` when compared
to the golden files.
See: `ClassifierCommonizationFromSourcesTest#testClassKindAndModifiers`.

Author: lunakoly

native/commonizer/src/org/jetbrains/kotlin/commonizer/metadata/flags.kt

@@ -94,10 +94,8 @@ internal fun KmTypeAlias.modifiersFrom(ct: CirTypeAlias) {
 private inline val CirHasAnnotations.hasAnnotations: Boolean
     get() = annotations.isNotEmpty()
 
-// Since 1.4.30 a special @JvmInline annotation is generated to distinguish JVM-inline from value classes.
-// This has an effect on class serialization: Every class with isValue == true automatically gets HAS_ANNOTATIONS flag.
 private inline val CirClass.hasAnnotations: Boolean
-    get() = annotations.isNotEmpty() || isValue
+    get() = annotations.isNotEmpty()
 
 private inline val CirProperty.hasAnnotations: Boolean
     get() = annotations.isNotEmpty() || backingFieldAnnotations.isNotEmpty() || delegateFieldAnnotations.isNotEmpty()