Asset name changes

[Gaurav0]

When we change the name / variant / path of an asset we break old imports and urls. We might be able to mitigate some of these changes and keep old imports and urls working by adding the legacy information to sheet definitions and then using that information at runtime to keep old imports and urls working.

Would this be worth it?

[jrconway3]

Maybe something like this, example from recent PR:

"belt_other_female": {
    "name": "Other belts",
}
...
    "variants": [
      "leather",
      "silver",
      "teal",
      "white"
    ],

I think the only realistic way to do it would be in the new one, so in there we need to add alternate mapping somewhere, such as:

    "aliases": [
        "belt=Other_belts_leather",
    ],

So basically, aliases would be where we allow other naming conventions to match this one. It has to be an exact match, though.