Introduce infrastructure to separate string table from metadata on JVM

Nothing especially helpful happens here, this is only a big refactoring
introducing a separate string array for the string table, which is currently
always empty, but will contain actual strings soon

core/runtime.jvm/src/kotlin/jvm/internal/KotlinCallable.java

@@ -30,4 +30,6 @@ public @interface KotlinCallable {
     int[] version() default {};
 
     String[] data();
+
+    String[] strings();
 }

core/runtime.jvm/src/kotlin/jvm/internal/KotlinClass.java

@@ -33,6 +33,8 @@ public @interface KotlinClass {
 
     String[] data();
 
+    String[] strings();
+
     enum Kind {
         CLASS,
 

core/runtime.jvm/src/kotlin/jvm/internal/KotlinFileFacade.java

@@ -30,4 +30,6 @@ public @interface KotlinFileFacade {
     int[] version() default {};
 
     String[] data();
+
+    String[] strings();
 }

core/runtime.jvm/src/kotlin/jvm/internal/KotlinMultifileClass.java

@@ -30,4 +30,6 @@ public @interface KotlinMultifileClass {
     int[] version() default {};
 
     String[] filePartClassNames();
+
+    String[] strings();
 }

core/runtime.jvm/src/kotlin/jvm/internal/KotlinMultifileClassPart.java

@@ -32,4 +32,6 @@ public @interface KotlinMultifileClassPart {
     String multifileClassName();
 
     String[] data();
+
+    String[] strings();
 }

core/runtime.jvm/src/kotlin/jvm/internal/KotlinPackage.java

@@ -30,4 +30,6 @@ public @interface KotlinPackage {
     int[] version() default {};
 
     String[] data();
+
+    String[] strings();
 }