fix: oauth_.fetch invocation on github_server and google_server

[brunoeduardodev]

Description

This PR fixes the invocation of the OAuth._fetch() method on the github_server and google_server of their oauth.
This fix is explained in more details on the Additional Notes of the Issue #13152.

I've set the base of the Pull Request as release-3.0 since the devel branch seems to not be fully updated with the code on release-3.0 (on the devel branch, this implementation was still using Fetch API and findOne invocations.)

[CLAassistant]

All committers have signed the CLA.

[netlify]

✅ Deploy Preview for v3-migration-docs canceled.

Name	Link
🔨 Latest commit	2c2dd3a
🔍 Latest deploy log	https://app.netlify.com/sites/v3-migration-docs/deploys/664f586f4fdf700008062773

[netlify]

✅ Deploy Preview for v3-meteor-api-docs canceled.

Name	Link
🔨 Latest commit	2c2dd3a
🔍 Latest deploy log	https://app.netlify.com/sites/v3-meteor-api-docs/deploys/664f586ffb7b550008a5fac4

[nachocodoner]

Thanks for this fix!

I adapted all account packages in my PR #13127. During this process, I provided tests with mocks, since these packages had side effects involving external cloud services that can't be tested easily. To do this, I used the standard OAuth._fetch, as in other packages. However, I missed an interface difference in the process.

I will pay more attention to interfaces in Meteor codebase, which lacks clear type-checking, above all on refactors on packages without coverage. And of course, more manual testing even when many scenarios affected. Regarding tests on this regression, I can't think of a way to properly verify behavior other than parameter checking, but I don't think it's necessary.

[denihs]

Hey @brunoeduardodev, I've just bumped the version for those packages, so you don't need to wait until the release:

google-oauth@1.4.5-rc300.3
github-oauth@1.4.2-rc300.3

[brunoeduardodev]

thanks!!