[#4418] Add addressNl specific mappings to Objects API registration (variables tab)

[vaszig]

Closes #4418

Changes

This PR handles the frontend part of the task

• Added specific addressNL fields/mappings to the Objects API registration (backend-frontend)
• Added stories

Checklist

Check off the items that are completed or not relevant.

• Impact on features

  • Checked copying a form
  • Checked import/export of a form
  • Config checks in the configuration overview admin page
  • Problem detection in the admin email digest is handled

• Release management

  • I have labelled the PR as "needs-backport" accordingly

• I have updated the translations assets (you do NOT need to provide translations)

  • Ran ./bin/makemessages_js.sh
  • Ran ./bin/compilemessages_js.sh

• Commit hygiene

  • Commit messages refer to the relevant Github issue
  • Commit messages explain the "why" of change, not the how

[codecov]

Codecov Report

Attention: Patch coverage is 97.61905% with 1 line in your changes missing coverage. Please review.

Project coverage is 96.60%. Comparing base (d985471) to head (8371e62).
Report is 2 commits behind head on master.

Files with missing lines	Patch %	Lines
...ons/contrib/objects_api/submission_registration.py	94.44%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #4751   +/-   ##
=======================================
  Coverage   96.60%   96.60%           
=======================================
  Files         749      749           
  Lines       25540    25575   +35     
  Branches     3377     3384    +7     
=======================================
+ Hits        24674    24708   +34     
  Misses        604      604           
- Partials      262      263    +1     

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

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[vaszig]

FYI, we have to take into consideration the old forms that they already may have addressNL variable_mappings configured. We may need a data migration for this.

[sergei-maertens]

Functional remarks:

• Is it possible to disable/remove the "map to geometry field" row/option when configuring an AddressNL component?

• The checkbox looks a bit odd because the label is specified before the checkbox itself:
  

  Standard Django form styling puts this in a different order:

  

  If we change this (please do), then I think the "map geometry field" needs the same treatment :)

• The "show json schema" component doesn't seem to make a lot of sense when mapping specific sub-components

  

  "Normally" this shows the json schema of the selected property from the object type when selecting a target path. This isn't relevant when mapping in more detail, unless you use this component for each nested target path, which will probably clutter too much, so I'd just not display it at all when mapping the sub components.

[vaszig]

Just a reminder for the translations and for #4751 (comment)

[sergei-maertens]

Just a reminder for the translations and for #4751 (comment)

I will do translations separately and I'll take a look at the data migration remark.