Install full SSL certificate chain for wp.dailp.northeastern.edu

Jira: https://dailp.atlassian.net/browse/DP-289?atlOrigin=eyJpIjoiM2Q5MDA1MGQ2Njc3NDczMWE3NTA5ZGZiMWJhNTVhY2IiLCJwIjoiaiJ9

This should fix our issues with WordPress for now. This is a dirty stopgap, but isn't unsafe. We are providing a real certificate. I've already reached out on the NEU-LTS slack so we can start working towards a more long-term solution.

How and why this works

Codegen has been failing to pull the WP GraphQL schema. This is because when the WordPress site got a new SSL certificate on December 18th, the server stopped providing a full certificate chain. This does not cause issues in the browser, because most browsers will do the work to fill in the gaps on the chain. NodeJS (where our tooling runs) will not. Installing the certificate locally like this means that Node will be very happy with https://wp.dailp.northeastern.edu, which is what we need to move forward. I got this certificate chain by clicking the "lock" on the address bar on firefox, viewing the certificate details, and then using the option to download the chain as a .pem file.

Commits:

update gql tooling -- I had to do this to get a more intelligent error when the fetch failed
install wp cert -- Allows node to happily pull the schema
updated schemas now that codegen works -- Diff spam resulting either from pulling the schema, or the version changes. I'm not worried because the typescript compiles.

Name	Link
Latest commit	5eb3877fedd86f0fe24084a443cc49f646b3808f
Latest deploy log	https://app.netlify.com/sites/dailp/deploys/6585d798ad32ea0008017a5b
Deploy Preview	https://deploy-preview-376--dailp.netlify.app
Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

NEU-DSG / dailp-encoding