fix: 🐛 generate array/non-scalar fields

[kekami]

use non-mapped table name to generate array/non-scalar fields on relational queries

✅ Closes: #2581

Description of changes

Fix issue where the generated AppSync DataResolverFn for relational SQL queries did not have arrayFields and nonScalarFields correctly set, e.g.

#set( $lambdaInput.args.metadata.arrayFields = [] )
#set( $lambdaInput.args.metadata.nonScalarFields = [] )

This was due to using the incorrect (mapped) tableName when generating these fields, e.g. tasks instead of Task

 constructArrayFieldsStatement(tableName, ctx),
 constructNonScalarFieldsStatement(tableName, ctx),

Issue #, if available

#2581

Description of how you validated changes

Unsure if it could be tested in a better way

Checklist

• PR description included
• yarn test passes
• Tests are changed or added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[palpatim]

Great find! Thanks for the troubleshooting and especially the fix with tests. Reviewing this now.

[palpatim]

Thanks again for this PR! I cherry picked your commits to #2689 so we could more easily resolve conflicts / rebase against main, and run E2E tests. It is now merged, and will be released during our next regular release.

[kekami]

Thanks again for this PR! I cherry picked your commits to #2689 so we could more easily resolve conflicts / rebase against main, and run E2E tests. It is now merged, and will be released during our next regular release.

Thank you, happy to help 🙌