feat(stripe): add api_version server option

[burmecia]

What kind of change does this PR introduce?

This PR is to add a new api_version foreign server option for Stripe FDW. Fix #291 .

What is the current behavior?

The current Stripe API requests are always using latest Stripe API version the version specified in the per-account settings, which can cause issues when requesting legacy Stripe API.

What is the new behavior?

Add a new api_version foreign server option, so users can specify a specific Stripe API version number when creating a foreign server.

More details about Stripe API versioning: https://docs.stripe.com/api/versioning

Additional context

N/A

[vickkhera]

Your "current behavior" description is backwards. Unless overridden per API call, the stripe API calls will use the version specified in the per-account settings for the API which may be too old for the queries this extension is using, as per my original bug report.

[imor]

@vickkhera updated the description. More importantly, now users should be able to specify the Stripe API version they want to use via the new option. Does that work for you?

[vickkhera]

@imor This is a workable solution. My solution was to just bump the version of the API in the Stripe dashboard, since I had nothing else using the API that might break with a newer version.

The docs https://supabase.github.io/wrappers/stripe/ should mention something about old versions being incompatible with this extension.

I still have this nagging feeling that the right thing in the clients using the API is to specify the version to which they are built, but I see no guidance from Stripe regarding that.

Thanks for following up.