Storage:copy is leading to misleading logo copying

[b0rt]

on a clean laravel installation with apidoc-generator
using a absolute logo path in conf/apidoc.php leads to copiying of logo to a different directory then the $outputPath defined in 'output' config depending on the configured filesystems in laravels conf/filesystems.php

The reason is (as for my investigations) the usage of Storage::copy in GenerateDocumentation

[b0rt]

on a side node: i propose to move the whole copy process of GenerateDocumentation to use https://laravel.com/docs/5.7/filesystem as it seems the cleaner way to do it.. deployment scenarios vary and the apidoc deployment could (if using laravel filesystem disks) be deployed on a specific 'disk' other than hard coded directory.

a similar discussion happens here and i am referencing it to further validate my thougths #373 .

[shalvah]

I'd accept a PR to do the conversion to the filesystem, but it needs to be done in a Lumen-compatible way. Or we could use Flysytem.🤔