feat(oauth/refresh-token): Add twitter provider

[jnv]

Description

Follow up to #196. This adds the Twitter as a oauth/refresh-token provider in addition to these changes:

• Profile also returns refreshToken which Twitter issues on every refresh
• Tests redact the refresh_token in the response
• Since new refresh token invalidates a previous one, I have settled with shared mutable object (currentInput) in tests to pass the refresh token between tests; it's not pretty so if you have a better solution, I am up for it
• Also the Twitter test logs out TWITTER_REFRESH_TOKEN on recording so an updated value can be pasted into .env

Technically adding a new property to result is a minor change, but I'd like to merge this along with #196 which isn't yet released, so there's no need for version change.

Motivation and Context

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [x] I have read the CONTRIBUTING document.
• [x] I haven't repeated the code. (DRY)
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.

[janhalama]

I'd like to merge this along with https://github.com/superfaceai/station/pull/196 which isn't yet released, so there's no need for version change.

Publishing is triggered by GA after merging to main. How are you goign to avoid running publish action for https://github.com/superfaceai/station/pull/196?

[jnv]

@janhalama Publishing is triggered by GA after merging to main. How are you goign to avoid running publish action for https://github.com/superfaceai/station/pull/196?

Will the publishing of 196 prevent me from publishing this one? My point is that the initial version will be so short-lived it won't break anything for anyone (and Google APIs map doesn't need any change).

But if this is a problem, I could merge this PR into 196 and then publish it in one go.

[jnv]

Alternatively I could just cancel the CI action once I merge #196...

[janhalama]

Will the publishing of 196 prevent me from publishing this one?

Yes, Brain response will be:

I am ok with proposed solutions.