refactor(location): allow postcode_by_state to take an array of patterns

[matthewmayer]

ref #3169

This change will make it easier to handle ZIP codes where there are "holes" in the ranges.

For example Hawaii could use two ranges like this to exclude 96799 (American Samoa)

HI: [
    '{{number.int({"min": 96701,"max": 96798})}}',
    '{{number.int({"min": 96801,"max": 96898})}}',
  ],

Since faker.helpers.fake accepts an array, just need to change the type. Will change the actual definitions in a followup PR.

[netlify]

✅ Deploy Preview for fakerjs ready!

Name	Link
🔨 Latest commit	dfab837
🔍 Latest deploy log	https://app.netlify.com/sites/fakerjs/deploys/670bd83c2b43df0008c7c503
😎 Deploy Preview	https://deploy-preview-3170.fakerjs.dev
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.96%. Comparing base (a8dfa2f) to head (dfab837).
Report is 1 commits behind head on next.

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #3170      +/-   ##
==========================================
- Coverage   99.97%   99.96%   -0.01%     
==========================================
  Files        2798     2798              
  Lines      227808   227808              
  Branches      580      955     +375     
==========================================
- Hits       227748   227733      -15     
- Misses         60       75      +15     

Files with missing lines	Coverage Δ
src/definitions/location.ts	100.00% <ø> (ø)

... and 1 file with indirect coverage changes

[xDivisionByZerox]

Sounds reasonable. Would we change the definition property type to only string[] in v10?

[ST-DDT]

I'd prefer using actual code instead of string patterns for v10.

• Proposal: Replace internal fake patterns with a resolver function #3176