feat(metadata): add method to access metadata

[matthewmayer]

fix #1984

[codecov]

Codecov Report

Merging #2143 (11121d8) into next (19635a7) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #2143      +/-   ##
==========================================
- Coverage   99.59%   99.59%   -0.01%     
==========================================
  Files        2623     2623              
  Lines      245491   245504      +13     
  Branches     1149     1152       +3     
==========================================
+ Hits       244503   244514      +11     
- Misses        961      963       +2     
  Partials       27       27              

Impacted Files	Coverage Δ
src/faker.ts	92.05% <100.00%> (+0.19%)	⬆️

... and 2 files with indirect coverage changes

[xDivisionByZerox]

I'm a bit conflicted about why we extract the metaobject access from the definitions. Currently, you can access them fine just fine via faker.definitions.metadata. What is the benefit of the implementation of this PR?

[matthewmayer]

I'm a bit conflicted about why we extract the metaobject access from the definitions. Currently, you can access them fine just fine via faker.definitions.metadata. What is the benefit of the implementation of this PR?

1. its not documented
2. we want the freedom to be able to rearrange things within definitions without it being a breaking change.

[Shinigami92]

Do not merge yet, so we can release a v8.0.2 the next few days
Generally do not merge feat+ into next, only fix, chore, test and docs