feat(locale): add Dutch province abbreviations

[RobinvanderVliet]

According to: https://en.wikipedia.org/wiki/ISO_3166-2:NL

[codecov]

Codecov Report

Merging #2232 (7c4d7a3) into next (5a48282) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #2232      +/-   ##
==========================================
- Coverage   99.60%   99.60%   -0.01%     
==========================================
  Files        2639     2640       +1     
  Lines      245741   245757      +16     
  Branches     1158     1156       -2     
==========================================
+ Hits       244771   244779       +8     
- Misses        943      951       +8     
  Partials       27       27              

Impacted Files	Coverage Δ
src/locales/nl/location/index.ts	100.00% <100.00%> (ø)
src/locales/nl/location/state.ts	100.00% <100.00%> (ø)
src/locales/nl/location/state_abbr.ts	100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

[xDivisionByZerox]

While I already approve, it would be nice if you could already sort the values alphabetically (a-z). We plan on
enforcing this via the locale generation script in the future. So if you could already do this we could reduce the git diff in the future :)

[RobinvanderVliet]

While I already approve, it would be nice if you could already sort the values alphabetically (a-z). We plan on enforcing this via the locale generation script in the future. So if you could already do this we could reduce the git diff in the future :)

I intentionally kept them in the same order as state.ts, because I thought the two files were connected in some way.

If that is not needed, I can order them alphabetically.

[ST-DDT]

I intentionally kept them in the same order as state.ts, because I thought the two files were connected in some way.

If that is not needed, I can order them alphabetically.

No, the files aren't connected with each other, so please sort this one alphabetically.
We keep connected data in the same file so they can be changed in one step and dont risk them diverging from each other. See also our airline.airline data.

[RobinvanderVliet]

I sorted them in this pull request and also in #2233.

[matthewmayer]

@RobinvanderVliet don't worry about merging next into your PR branches, this will be done automatically before the feature is squash merged. You only need to bother if there are conflicts.