Add links to tile provider authentication docs

[ianthetechie]

This probably confused some people in the past, since vector tiles won't even display an access denied image ;)

Before (no information on access keys and where to get them):

After (add links to providers in info callout + add a field for Stadia Maps API keys):

[zstadler]

Should there also be a "Stadia Maps Access Token" field?

[ianthetechie]

Should there also be a "Stadia Maps Access Token" field?

It's not required for most web browser uses; I'll add one either this weekend or Monday.

I see I also missed updating(?) some tests. Will look at that too.

[nyurik]

@HarelM any blockers for this one?

[HarelM]

Yes, translation is now needed for text.
Also the above comment about adding an input for the token was not addressed.

[ianthetechie]

Got side tracked on a few other projects, but got back to adding the token support in the latest edits.

Thanks for letting me know about the translation @HarelM! I didn't know that was a thing 😅 I've also added a few lines explaining that to the README.

[HarelM]

Yes, translation was added very recently.
Other than the above, this looks good.
It would be great if you can update the initial post with "before" and "after" screenshots.

[HarelM]

Thanks!
Should there be an input for stadia maps api key?

[HarelM]

Wait, what about the translation of the text you added?

[ianthetechie]

Ack.

1. I didn't update the "after" screenshot.
2. I think I didn't add the i18n bits for top-level help text I added (it didn't exist when I added that?

I'll address both momentarily.

[ianthetechie]

Hmm... I wonder if it is easier to localize these as separate help text strings... I don't know the grammatical structure of Hebrew, but I imagine there is some language where it might be complicated to do this all correctly.

Thoughts on moving it out of the single header text to the expandable help? Here's what it looks like now:

[ianthetechie]

Ick; that's going to be fun... Sorry I'm not much of a frontend dev, but it looks the HTML is being escaped if I try specifying strings this way...

So it's going to be a bit of work with either approach :/

[HarelM]

I think adding a description like other fields is a good idea.

[ianthetechie]

Okay. This will take some effort to untangle (for me at least). Even adding a relatively simple "learn more" link along with the help text is proving to be difficult.

I was able to get this far with it, but hit two roadblocks:

1. I can't figure out how to get a t function down to translate the learn more link text.
2. The link is valid, and it fires an onClick handler, but left click doesn't work. I assume something in the hierarchy is preventing propagation.

[ianthetechie]

Took a while for me to get back to this again, but I overcame the event and i18n issues finally ;)

The only thing remaining is getting the new strings translated. I also see the i8n plugin keeps weirdly rewriting the file, so a bit of manual cleanup required for some strings.

[HarelM]

Looks good, thanks!
Tagging the translators:
de German @josxha
en English @HarelM
fr French @lhapaipai
hr Hebrew @HarelM
ja Japanese @keichan34
zh Simplified Chinese @jieme

[ianthetechie]

Ok... I think the only outstanding item now are translations from @keichan34 @jieme

[HarelM]

We'll give it a few days and then decide if we merge as is or do something else.

[HarelM]

I'll merge it like that, if people are interested in seeing Maputnik in their language, they can contribute the relevant translation I guess...