🐛 [#2665] Fix phone-parsing Safari (iOS only)

[jiromaykin]

Taiga: https://taiga.maykinmedia.nl/project/open-inwoner/issue/2665

The turn-numbers-into-phone-links feature should be disabled with the format-detection meta-tag, but... on every Safari and iOS update this breaks again 😡; many users on new devices report the meta tag does not solve the problem, so we need to create a hack with pointer-events is zero and add a zero-width joiner ‍ to make the numbers unrecognizable.
I've also added these to the Zaaknummers e-mail templates, since those are also parsed in iOS.

While I was reproducing all this in Browserstack I found a bug in the skip-link specific for Safari only, which is also solved here.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.21%. Comparing base (65b1058) to head (2bcc9a0).
Report is 48 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1369      +/-   ##
===========================================
- Coverage    94.23%   94.21%   -0.02%     
===========================================
  Files         1068     1074       +6     
  Lines        39348    39621     +273     
===========================================
+ Hits         37080    37330     +250     
- Misses        2268     2291      +23     

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

[pi-sigma]

Small suggestion for the new CSS class name, otherwise looking good. Browserstack is currently not working for me, I'll need to try again to test this.

[pi-sigma]

Suggested change

	.phone-parsing {
	.skip-phone-parsing {

or something like it so that the function of the class is clear from the name alone (otherwise you have to come hear to look at the comment)

[jiromaykin]

Ah, yeah, good one, will do.

[pi-sigma]

Suggested change

	.phone-parsing > a {
	.skip-phone-parsing > a {

[pi-sigma]

Suggested change

	.phone-parsing > a {
	.skip-phone-parsing > a {

[pi-sigma]

Suggested change

	.phone-parsing {
	.skip-phone-parsing {

[jiromaykin]

...Browserstack is currently not working for me, I'll need to try again to test this.

@pi-sigma Actually I was not able to replicate this problem in Browserstack. Meaning: if I keep the meta-tag in the Master template as is <meta name="format-detection" content="telephone=no">, then it doesn't really matter which iphone or iOS version you choose in Browserstack, the formatting there is correctly turned off for any number. So the bug actually doesn't happen there, but I am guessing this is because Browserstack probably is not a full 100% native device. This is quite obscure.
But Hendrik specifically said the formatting problem comes back on his specific device (an iPhone mini with iOS 12 Safari) so for testing I took out the meta-tag and looked at what happens with the other code changes in place.