Expose oss-directory social data in projects_v1 API

[ryscheng]

We are currently missing socials and website I think

[ryscheng]

One idea is expose all twitter handles as artifacts, which you can query via artifacts_by_project. Something like artifact_source=TWITTER artifact_name=@handle Should artifact_namespace be null?

which kinda sets us up for tracking twitter events in the future, like farcaster events, which we're already starting to work on

[mseidlx]

@ryscheng I like the idea of exposing socials via artifacts! In my mind it probably makes sense to expose all 1:n relationships via artifacts_by_project

[ryscheng]

Done here https://github.com/opensource-observer/oso/pull/2078