Add option to update project imagery API key

[laurentS]

The api key for maxar imagery seems to be rotated fairly frequently. When this happens, users have no imagery at all, and only a (small) handful of us of are able to unblock the situation, which is a major problem for urgent projects.

It would be helpful to have some way to update projects imagery api key from the management dashboard. Suggested workflow:

• add a update maxar imagery key button somewhere under each project box
• upon clicking, that button opens an input box that allows inputting the new API key value (and has some validity check to limit risks of typos, etc...)
• once validated, the project settings in firebase are updated

This should allow anyone with manager permissions to fix their own (and other) projects, which hopefully would remove that bottleneck.

[danbjoseph]

For anyone with access to the backend server, @Hagellach37 previously added an automated way to update all affected projects. Should we have a sort of "system" page as part of the management dashboard that provides a UI for things like this?

python-mapswipe-workers/Makefile

Lines 29 to 30 in df276f7

	update_tms_api_key:
	@echo "first update the .env file with the new api key and then run this script with tms_name=your_tms_provider_name to update API key"; docker compose run --rm mapswipe_workers_creation python python_scripts/change_tms_api_key_for_projects.py $(tms_name)

---

@danbjoseph: if we are grabbing the JOSM key, is MapSwipe causing the “conspicuous usage pattern” that is mentioned in the JOSM issue as causing Maxar to rotate the key?

@Hagellach37: we had an exchange around this about 2-3 years ago, when this came up the first time and together with someone from Maxar we concluded that it is not MapSwipe. The volume was much much bigger than what we do usually