fix: update JS/TS MIPR

Author: phani-srikar

packages/appsync-modelgen-plugin/src/__tests__/visitors/__snapshots__/appsync-json-metadata-visitor.test.ts.snap

@@ -615,7 +615,8 @@ exports[`Metadata visitor for custom PK support relation metadata for hasOne/bel
                     \\"association\\": {
                         \\"connectionType\\": \\"HAS_ONE\\",
                         \\"associatedWith\\": [
-                            \\"project\\"
+                            \\"id\\",
+                            \\"name\\"
                         ],
                         \\"targetNames\\": [
                             \\"projectTeamId\\",
@@ -795,7 +796,8 @@ export const schema: Schema = {
                     \\"association\\": {
                         \\"connectionType\\": \\"HAS_ONE\\",
                         \\"associatedWith\\": [
-                            \\"project\\"
+                            \\"id\\",
+                            \\"name\\"
                         ],
                         \\"targetNames\\": [
                             \\"projectTeamId\\",

packages/appsync-modelgen-plugin/src/visitors/appsync-javascript-visitor.ts

@@ -47,9 +47,11 @@ export class AppSyncModelJavascriptVisitor<
     const shouldUseModelNameFieldInHasManyAndBelongsTo = false;
     // This flag is going to be used to tight-trigger on JS implementations only.
     const shouldImputeKeyForUniDirectionalHasMany = true;
+    const shouldUseFieldsInAssociatedWithInHasOne = true;
     this.processDirectives(
       shouldUseModelNameFieldInHasManyAndBelongsTo,
-      shouldImputeKeyForUniDirectionalHasMany
+      shouldImputeKeyForUniDirectionalHasMany,
+      shouldUseFieldsInAssociatedWithInHasOne
     );
 
     if (this._parsedConfig.isDeclaration) {

packages/appsync-modelgen-plugin/src/visitors/appsync-json-metadata-visitor.ts

@@ -114,9 +114,12 @@ export class AppSyncJSONVisitor<
     const shouldUseModelNameFieldInHasManyAndBelongsTo = false;
     // This flag is going to be used to tight-trigger on JS implementations only.
     const shouldImputeKeyForUniDirectionalHasMany = true;
+    const shouldUseFieldsInAssociatedWithInHasOne = true;
+
     this.processDirectives(
       shouldUseModelNameFieldInHasManyAndBelongsTo,
-      shouldImputeKeyForUniDirectionalHasMany
+      shouldImputeKeyForUniDirectionalHasMany,
+      shouldUseFieldsInAssociatedWithInHasOne
     );
 
     if (this._parsedConfig.metadataTarget === 'typescript') {

packages/appsync-modelgen-plugin/src/visitors/appsync-typescript-visitor.ts

@@ -44,9 +44,11 @@ export class AppSyncModelTypeScriptVisitor<
     const shouldUseModelNameFieldInHasManyAndBelongsTo = false;
     // This flag is going to be used to tight-trigger on JS implementations only.
     const shouldImputeKeyForUniDirectionalHasMany = true;
+    const shouldUseFieldsInAssociatedWithInHasOne = true;
     this.processDirectives(
       shouldUseModelNameFieldInHasManyAndBelongsTo,
-      shouldImputeKeyForUniDirectionalHasMany
+      shouldImputeKeyForUniDirectionalHasMany,
+      shouldUseFieldsInAssociatedWithInHasOne
     );
     const imports = this.generateImports();
     const enumDeclarations = Object.values(this.enumMap)