@0xMochan @joshua-mo-143 please let me know if this is correct approach

TBH, i'm not too fond of a crate (even if internal) that is only used to reduce duplication among examples. the examples' duplications come from the fact that we lack a proper integration testing suite. internally, we've discussed introducing and rolling some examples as apart of said suite on running against commits against our release branches. since these only get bumped on the PRs that get merged (+ we can always cancel if needed), it'll ensure that we don't burn too many credits in testing.

Then, we can skim through and try to isolate examples that actually highlight a specific use-case (rather than just duplicating every example for every provider). There's also a case of some examples that highlight openai-compatible services that could be collapsed into a single example, though I'm not entirely sure what that would look like.

If there is an examples crate in the wild that does use a shared / example crate as a form of reducing duplication, i'd love to get a look as an alternative perspective on this.