🎉 lightning chart deploys

[Marigold]

Problem

Updating a chart enqueues a full deploy that can take >15min and is prone to errors (due to high load on external servers like R2 or Spaces). Deploying only a single chart could significantly speed up most deploys.

Solution

• Add the bakeCharts command that is very similar to bakeGDocs, which takes care of GDocs lightning deploys
• Trigger a deployment after clicking on Update chart or Publish buttons
• Lightning build with chartSlug goes to deploy queue which triggers BuildkiteJob OWID - deploy content with env variable LIGHTNING_CHART_SLUGS
• Buildkite runs bakeCharts --slugs LIGHTNING_CHART_SLUGS on the server, syncs grapher/exports with generated png & svg to R2 and then deploys the site to Cloudflare

Potential issues

What other things need to happen when we publish or update a chart? Perhaps updated redirects might require full rebuild or at least rebuilding of redirects file in Buildkite.

Things that could be affected by updated chart (need to check)

• explorer based indicators
• prominent links

[github-actions]

This PR has had no activity within the last two weeks. It is considered stale and will be closed in 3 days if no further activity is detected.

[Marigold]

Longer discussion on slack. It's not clear whether this is worth merging. We should ask authors if they're even interested in this.

[ikesau]

From Gdocs, prominent links to gdocs are already broken which means they're probably not used anywhere.

There are still WP articles that use (working) prominent links for graphers though 😢

[danyx23]

@Marigold we'll try to do a product hour about gdocs at some point soon and then ask authors how much this is bothering them. Suggest we keep this open until then.

[Marigold]

@danyx23 good. I was gonna ask, but thought I'd wait for Matthieu's build notifications first. Maybe these are the answer rather than faster builds.

[github-actions]

This PR has had no activity within the last two weeks. It is considered stale and will be closed in 3 days if no further activity is detected.

[Marigold]

It turned out authors don't really need this. It could still be useful for approving charts that trigger chart updates and it could eliminate freezing of admin, but it's probably not worth at this point.