fix: add condition to pick correct schemas for fixed array items in topathschemainternal util

[Rozamo]

Reasons for making this change

Fixes #3909.

Changes

• Adds condition to generate correct path schemas for schemas containing fixed array of items in the toPathSchemaInternal util. The items property for these schemas are of array type instead of object. Because the condition for the array type items was not present, the array type schema was being sent into the recursive function as the schema for the form data, which was not matching. Hence empty form data was being generated each time Form's onChange was being called
• Adds tests for the above change ensuring 100% coverage for the toPathSchema util

Checklist

• I'm updating documentation
  • I've checked the rendering of the Markdown text I've added
• I'm adding or updating code
  • I've added and/or updated tests. I've run npm run test:update to update snapshots, if needed.
  • I've updated docs if needed
  • I've updated the changelog with a description of the PR
• I'm adding a new feature
  • I've updated the playground with an example use of the feature

[heath-freenome]

I'm wondering whether there should be a console.warn or console.error for this condition?

[Rozamo]

I can see that toPathSchema util is mostly used as a step to omit extra data. In that case should we warn the users about the omitted data?

[heath-freenome]

For the moment, let's add a console.warn() here to let users know that they have unhandled formData. Which means we want to update the test below with a check that console.warn() was called. This can be done with a jest.spyOn()

[Rozamo]

Sure. Added a message. Let me know if there is a change required.

[Rozamo]

@heath-freenome Should this log be moved up a level outside the for loop? We don't know how many items there will be in the array and if there are too many items, it might clutter the console.