feat: add appconfig endpoint

[jamesgorrie]

As per this diagram - a step to work towards having a server side rendered page would be to make the app config accessible via a URL that a node app could read and render from.

This starts us on that journey.

Here's the full diagram with the end goal, the part this is focussing on is labelled "This PR" in purple.

[github-actions[bot]]

Deploy build 11121 of support::stripe-patrons-data to CODE

All deployment options

- [Deploy build 11121 of `support::stripe-patrons-data` to CODE](https://riffraff.gutools.co.uk/deployment/deployAgain?project=support%3A%3Astripe-patrons-data&build=11121&stage=CODE&updateStrategy=MostlyHarmless&action=deploy) - [Deploy parts of build 11121 to CODE by previewing it first](https://riffraff.gutools.co.uk/preview/yaml?project=support%3A%3Astripe-patrons-data&build=11121&stage=CODE&updateStrategy=MostlyHarmless) - [What's on CODE right now?](https://riffraff.gutools.co.uk/deployment/history?projectName=support%3A%3Astripe-patrons-data&stage=CODE)

---

From guardian/actions-riff-raff.

[github-actions[bot]]

Size Change: 0 B

Total Size: 2.25 MB

ℹ️ View Unchanged

| Filename | Size | | :--- | :---: | | `./public/compiled-assets/javascripts/[countryGroupId]/events/router.js` | 112 kB | | `./public/compiled-assets/javascripts/[countryGroupId]/router.js` | 254 kB | | `./public/compiled-assets/javascripts/ausMomentMap.js` | 108 kB | | `./public/compiled-assets/javascripts/contributionsRedirectStyles.js` | 20 B | | `./public/compiled-assets/javascripts/digitalSubscriptionLandingPage.js` | 241 kB | | `./public/compiled-assets/javascripts/downForMaintenancePage.js` | 69.4 kB | | `./public/compiled-assets/javascripts/error404Page.js` | 69.3 kB | | `./public/compiled-assets/javascripts/error500Page.js` | 69.3 kB | | `./public/compiled-assets/javascripts/favicons.js` | 617 B | | `./public/compiled-assets/javascripts/paperSubscriptionCheckoutPage.js` | 195 kB | | `./public/compiled-assets/javascripts/paperSubscriptionLandingPage.js` | 86.1 kB | | `./public/compiled-assets/javascripts/payPalErrorPage.js` | 67.8 kB | | `./public/compiled-assets/javascripts/payPalErrorPageStyles.js` | 20 B | | `./public/compiled-assets/javascripts/promotionTerms.js` | 72.5 kB | | `./public/compiled-assets/javascripts/subscriptionsLandingPage.js` | 71.6 kB | | `./public/compiled-assets/javascripts/subscriptionsRedemptionPage.js` | 126 kB | | `./public/compiled-assets/javascripts/supporterPlusLandingPage.js` | 309 kB | | `./public/compiled-assets/javascripts/unsupportedBrowserStyles.js` | 20 B | | `./public/compiled-assets/javascripts/weeklySubscriptionCheckoutPage.js` | 192 kB | | `./public/compiled-assets/javascripts/weeklySubscriptionLandingPage.js` | 86.1 kB | | `./public/compiled-assets/webpack/136.js` | 2.17 kB | | `./public/compiled-assets/webpack/272.js` | 18.1 kB | | `./public/compiled-assets/webpack/344.js` | 2.04 kB | | `./public/compiled-assets/webpack/430.js` | 81.8 kB | | `./public/compiled-assets/webpack/841.js` | 19.8 kB |

_{compressed-size-action}

[github-actions[bot]]

Deploy build 20385 of support:support-workers-mono to CODE

All deployment options

- [Deploy build 20385 of `support:support-workers-mono` to CODE](https://riffraff.gutools.co.uk/deployment/deployAgain?project=support%3Asupport-workers-mono&build=20385&stage=CODE&updateStrategy=MostlyHarmless&action=deploy) - [Deploy parts of build 20385 to CODE by previewing it first](https://riffraff.gutools.co.uk/preview/yaml?project=support%3Asupport-workers-mono&build=20385&stage=CODE&updateStrategy=MostlyHarmless) - [What's on CODE right now?](https://riffraff.gutools.co.uk/deployment/history?projectName=support%3Asupport-workers-mono&stage=CODE)

---

From guardian/actions-riff-raff.

[jamesgorrie]

Love the diagram. Which bits of it does config.json represent? Is it everything in Data fetching bar private config?

It is indeed - basically everything on the window.guardian object currently

[prout-bot]

Seen on PROD (merged by @jamesgorrie 10 minutes and 57 seconds ago)

• Keep an eye out for the post deployment tests github action
• If the tests have failed, the post deployment test runbook should help troubleshoot.

Sentry Release: support-client-side, support