fix: better determination of oneOf for hash arrays in hash arrays

[Spence1115]

Summary

Fixes #270

When a nested entry inside a response contained multiple possible types, we were only ever returning the first one. For example:

          {
            "fields" => [
              {
                "id" => "country_code",
                "options" => [
                  {
                    "id" => "us",
                    "label" => "United States"
                  },
                  {
                    "id" => "ca",
                    "label" => "Canada"
                  }
                ]
              },
              {
                "id" => "region_id",
                "options" => [
                  {
                    "id" => 1,
                    "label" => "New York"
                  },
                  {
                    "id" => 2,
                    "label" => "California"
                  }
                ]
              }
            ]
          }

For this, the id in options was being marked as type: string, when it should have been oneOf: string | number

This PR changes that, so now we get

{
    "options": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "oneOf": [
              {
                "type": "string"
              },
              {
                "type": "integer"
              }
            ]
          },
          "label": {
            "type": "string"
          }
        },
        "required": [
          "id",
          "label"
        ]
      }
    }
}

Additionally I've added more tests to cover different response shapes to try and ensure any further complexities are covered (along with simple versions), and to ensure all paths of the new code are covered. These may be excessive and I'm happy to cut back if desired.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.68%. Comparing base (204a75e) to head (9beb59d).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #269      +/-   ##
==========================================
- Coverage   97.26%   94.68%   -2.58%     
==========================================
  Files          20       20              
  Lines         695      734      +39     
  Branches      163      185      +22     
==========================================
+ Hits          676      695      +19     
- Misses         19       39      +20     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Spence1115]

Codecov Report

✅ All modified and coverable lines are covered by tests. ✅ Project coverage is 94.68%. Comparing base (204a75e) to head (9beb59d).

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #269      +/-   ##
==========================================
- Coverage   97.26%   94.68%   -2.58%     
==========================================
  Files          20       20              
  Lines         695      734      +39     
  Branches      163      185      +22     
==========================================
+ Hits          676      695      +19     
- Misses         19       39      +20     

☔ View full report in Codecov by Sentry. 📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

I'm not sure why overall project coverage is down when my branch has 100% coverage...

[exoego]

LGTM
Thank you