Spotify public key may change

[wildarch]

Since the last time I bootstrapped, spotify changed the key they used for their APT repository.

This caused APT update to fail, because the newly added spotify repo had an unrecognized key.

Ways to fix this:

• Use an ansible role that handles this for us. I could not find one that looks reasonably popular and/or well-maintained
• Switch to the snap version. I prefer not to because I have no other uses for snaps
• Periodically check https://www.spotify.com/us/download/linux for updates, perhaps in an automated fashion. Note: looks like the key url can be retrieved using curl+grep
• Find a different url for the key that automatically updates to the latest version

[wildarch]

A similar thing happens with zoom. We have to download a fixed version of it, and updating it requires manual work.

For zoom we get the latest version based on what https://zoom.us/client/latest/zoom_amd64.deb redirects us to (for example, at the time of writing it redirects to https://cdn.zoom.us/prod/5.11.0.3540/zoom_amd64.deb).

It might be nice to add a little script that can check for updates, and if possible also automatically update the WORKSPACE and/or ansible playbook.