Script to build OP Curations and cache the output

[ksen0]

Relates to #1187

This is marked as a draft because it is not clear if a different solution might be possible. Alternatives that I am investigating with OP in the next week-ish:

1. Use token + GH secret in build process and keep it during build process
2. Switch to client-side calls (thanks @doradocodes for your input on this)

If keeping build process, then need a better approach; even if caching, this particular script generates a large amount of checked in json files which is not ideal.

Full disclosure on AI use: copilot was used for the script, since I was on a time crunch for the fix.

[davepagurek]

Going to take a more thorough look later but I think generally checking in the cached content is still the way to go, similar to how our other pages on the site that are derived from other data work. Possibly a future approach just to minimize the amount of data could be, like what we do with reference and contributor docs and such, is to have the script transform the data into a more directly usable format instead of storing it verbatim? e.g. just the titles and sketch size or something. But storing the full data does give us a bit more flexibility to change what we do with it, so it's also not a bad approach at all