Fixing phpdoc for Resource::call method return type

[amackiewicz]

Found that issue by the way of using Google_Service_Drive->files->export.

Files::export calling Resource::call and returning its output. In normal circumstances it returns psr ResponseInterface, just in some cases (when request is defered) it returns RequestInterface.

Current @return in Resource::call method has 2 issues:

1. Its solid class Response instead of ResponseInterface
2. Its cheating IDE which dont know that File::export could return ResponseInterface which end up with code as following. Of course its triggers ERROR: TypeError: Return value of Foxstone\BackendPHP\service\GoogleDriveService::exportFileContents() must be an instance of GuzzleHttp\Psr7\Request, instance of GuzzleHttp\Psr7\Response returned

Example of generated code (type returns by exportFileContents method was inherited from types returns from File::export (and then from Resource::call) which is wrong):

    /**
     * @throws Exception
     */
    public function exportFileContents(
        string $fileId,
        string $exportMimetype
    ): ResponseInterface {
        $this->connect();

        return self::$GoogleServiceDrive->files->export(
            $fileId,
            $exportMimetype,
            ['alt' => 'media']
        );
    }

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[amackiewicz]

@googlebot I signed it!

[bshaffer]

@amackiewicz This looks great, although I'm not sure when it would return array for these functions. Can you elaborate?

[amackiewicz]

Hey @bshaffer ! well, me too :) but REST::execute phpdoc saying that it could return array (https://github.com/googleapis/google-api-php-client/blob/master/src/Http/REST.php#L44).
I've changed phpdoc also for that method, check it out plz

[amackiewicz]

any updates here @bshaffer ? :)