Description:
We are running Assets v.3.0.0 and have Wyvern set to use Assets as the file manager.

When editing content in Wyvern, if we select some content to create a link for the purposes of linking a file for download, when we go through the process, the URL ends up being {filedir_s3:3}https://s3.amazonaws.com/path/to/file.jpg, which breaks. This also happens when the file is stored locally rather than on S3: https://boldminded.com/assets/images/uploads/file-name.png.  If we remove that extra stuff at the front and click OK, it reverts to a link URL of type “Other” and cuts off the ‘https://’ portion, which creates a link on the page like: http://my-site.com/s3.amazonaws.com/path-to-file/jpg. In order to get the link to work, we have to then edit the link we just created, and add on the ‘https://’ portion manually.

Detailed steps to reproduce the issue:
1. Edit any entry that has a Wyvern field
2. Type some content in that field, select it, and click the Link button
3. Under “Link Type” select “File Asset”, and then click “Browse”. This opens the Assets overlay.
4. Select the file you want to link, and click “Add Files”.
5. The path that is populated in the “Asset Path” field has the extra data in front of it.

** As an additional note, I downloaded the latest version of Wyvern (2.0.0) from my purchases on devot-ee.com, but when installed it only says 1.8.0.