Consider using url as field name in provider scripts

[stacimc]

Current Situation

Currently in our provider scripts, we use a different field name per media type for the url field -- so, image_url and audio_url. In the actual database, these all just map to url, and so we have to manually convert the field name in each of the associated media stores (example in ImageStore).

Suggested Improvement

Unless there's a reason it must be done this way, I'd like to just use url everywhere.

Benefit

• We would be able to remove the MediaStore logic to convert the field name
• It would be much easier to document what fields are needed in provider scripts, and what they map to in the actual database.
• It would be much easier for providers that consume media of multiple types to deal with URLs. See here an example of Wikimedia needing to set the url, then later pop it off the data and rename it depending on the media type, only for it to just get changed back in the media store
• It would be much easier to define types for ImageData and AudioData.

Additional context

I'm unaware of the reasoning for the current implementation, so it's possible there's a critical reason why these fields are renamed and we should be sure to test thoroughly.

Implementation

• 🙋 I would be interested in implementing this feature.

[AetherUnbound]

Fully support this! I honestly wasn't even aware of this discrepancy until recently, even after working with the provider scripts for some time.

[obulat]

I tried finding a reason behind image_url as the field name, and couldn't. The database column name seems to always have been url, and the PR that adds ImageStore simply says that image_url in ImageStore corresponds to url in the database: cc-archive/cccatalog#246

I support the change 👍