feat(open-payments): export OpenAPI specs

[mkurapov]

Changes proposed in this pull request

• Export getAuthServerOpenAPI getResourceServerOpenAPI getWalletAddressServerOpenAPI functions from the open-payments package
• Move openapi/*yaml files into openapi/specs/

Context

Since we bundle the yaml files with the open-payments package, we should let users of the package (importantly for us, Rafiki) to fetch the OpenAPI objects for the Open Payments specs

Fixes #439

[changeset-bot]

🦋 Changeset detected

Latest commit: 083719f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@interledger/open-payments	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[netlify]

✅ Deploy Preview for openpayments-preview canceled.

Name	Link
🔨 Latest commit	083719f
🔍 Latest deploy log	https://app.netlify.com/sites/openpayments-preview/deploys/65f2ebfe94e942000886c7e1

[BlairCurrey]

Looks good to me. Will be nice to have an easier way to get the right spec version in rafiki.

I spent some time thinking about the path assertions in packages/open-payments/src/openapi/index.test.ts. I was just thinking they were more a concern of createOpenAPI (if anything - kinda just an implementation detail of the spec) but I suppose it makes sense as a sanity check and isn't hard to update when things change (and they dont change often).

[mkurapov]

@BlairCurrey good point, I was thinking along the same lines, but like you said, this is sanity checking createOpenAPI specifically in relation to the OP specs

[mkurapov]

@BlairCurrey also, what was cool is that I just pnpm-linked the package with the changes and ran it through your integration test as a sanity in Rafiki 👍