refactor(locale): unfreeze arrays

[Shinigami92]

closes #2890

[netlify]

✅ Deploy Preview for fakerjs ready!

Name	Link
🔨 Latest commit	0f58f5a
🔍 Latest deploy log	https://app.netlify.com/sites/fakerjs/deploys/665c7582f46a7a000878d833
😎 Deploy Preview	https://deploy-preview-2928.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.95%. Comparing base (a082ed2) to head (0f58f5a).

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #2928      +/-   ##
==========================================
- Coverage   99.95%   99.95%   -0.01%     
==========================================
  Files        2986     2986              
  Lines      215926   215926              
  Branches      598      945     +347     
==========================================
- Hits       215839   215833       -6     
- Misses         87       93       +6     

Files	Coverage Δ
src/locales/en/science/chemical_element.ts	100.00% <100.00%> (ø)
src/locales/en/science/unit.ts	100.00% <100.00%> (ø)
src/locales/eo/science/chemical_element.ts	100.00% <100.00%> (ø)
src/locales/eo/science/unit.ts	100.00% <100.00%> (ø)
src/locales/nb_NO/science/chemical_element.ts	100.00% <100.00%> (ø)
src/locales/nb_NO/science/unit.ts	100.00% <100.00%> (ø)
src/locales/pl/science/chemical_element.ts	100.00% <100.00%> (ø)
src/locales/pl/science/unit.ts	100.00% <100.00%> (ø)
src/locales/zh_CN/science/chemical_element.ts	100.00% <100.00%> (ø)
src/locales/zh_CN/science/unit.ts	100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

[xDivisionByZerox]

Multiple questions from my side:

1. Although the title's humor is appreciated, could we consider revising it to more accurately reflect the content of the change? This would enhance the final result of the autogenerated changelog.
2. I'd consider this change a refactor over a chore given the potential side-effects during runtime. Would you agree?
3. While these changes are not breaking, I believe it would be prudent to include a note in the migration guide for v9, informing developers that all our locale data will be mutable in future versions. Providing developers with advance notice may prevent frustration and avoidable inquiries. What do you think?

[Shinigami92]

1. Although the title's humor is appreciated, could we consider revising it to more accurately reflect the content of the change? This would enhance the final result of the autogenerated changelog.

done

2. I'd consider this change a refactor over a chore given the potential side-effects during runtime. Would you agree?

done

3. While these changes are not breaking, I believe it would be prudent to include a note in the migration guide for v9, informing developers that all our locale data will be mutable in future versions. Providing developers with advance notice may prevent frustration and avoidable inquiries. What do you think?

not sure, maybe we want to discuss? I think unfreeze wont affect the end-user in any way
If it would be the opposite (freezing objects) then it would have a potential negative effect if user did modify the objects