Add a schema for self-reporting

[chadwhitacre]

Light-weight self-reporting is a central part of the OSS Pledge. What should the format be? Let's define it using JSON Schema for easy validation and interoperability. Going with Zod as part of Astro since that's what we've set up in this repo.

(X reachout)

System Design

1. Companies host an osspledge.json on their own domain (think robots.txt).
2. We have a members.csv in this repo containing slug,url for members.
3. Joining Pledge is by PR to this repo, adding to members.csv
4. We have a GHA automation to update src/members/{slug}.json when members.csv changes.
5. We have another automation to update {slug}.json periodically based on modtime stored therein.

[chadwhitacre]

Now that we're ported to Astro I've ported this PR to Astro as well. It's going pretty well! :-)

[chadwhitacre]

Latest iteration in 1a198e9.

[chadwhitacre]

Point from @vladh on a call to use https://en.wikipedia.org/wiki/Well-known_URI

[vladh]

@chadwhitacre I might make some progress on this over the weekend if you're not opposed?

[chadwhitacre]

What are you thinking of working on? The next steps I have in mind are to add real numbers for Sentry and publish the json file on open.sentry.io. The next step after that would be to write the GitHub automations to modify files under src/collections/members/ when members.csv changes and periodically (to pick up changes to json files already listed in the csv). I just pushed a couple commits to this PR that I think brings it to a spot where we could merge, and then pick up with further work in new PRs. Sound like a plan?

[vladh]

Sounds good, will do that!