Clarity requested on Media Reference's target_url format

Hi there,

I was wondering if any of those 2 pages were slightly out of date regarding how the Media Refence target_url should be formatted by write adapters.
Of if read adapters should be handling both cases?

The read the docs page [here](https://opentimelineio.readthedocs.io/en/latest/tutorials/write-an-adapter.html#media-references) mentions it should have a `file://` prefix.
Where the unit tests [here](https://github.com/AcademySoftwareFoundation/OpenTimelineIO/blob/2429dd5cd35a16949b7b675c24aad61e123f064d/tests/test_media_reference.py#L47) mention it should be raw.

The confusion emerged from Adobe Premiere Beta 26.1 exporting OTIO files with media references with said `file://` prefix.
And DaVinci Resolve 20.2 failing to import OTIO files formatted that way. (manually removing those prefixes let DaVinci Resolve import them just fine)
Which has been an issue reported a year ago in the Adobe community [here](https://community.adobe.com/t5/premiere-pro-beta-discussions/now-in-beta-otio-import-and-export/m-p/14938190#M10400) , which can still be replicated today with above - recent - versions.

Best,
C

Start by comparing the Media References section in the write-adapter documentation with tests/test_media_reference.py, especially the linked lines. Resolve which target_url format adapters should use or accept, then make the documentation and tests consistent with that decision.

Written by the indexing model from the issue text.