Better interoperability with embedded info cards

Many times when we download a model (checkpoints, VAEs and so, but especially true for LORAs) and use it in other tools, like ComfyUI or Automatic 1111, it's hard to find the resource because the name of the file it's not the name of the resource at Civitai. Sometimes they don't have anything to do. Over time, when you forget about them and revisit your models you have no idea what that model is.

Perhaps we could add an embedded info card to (almost) every model file on civitai. The model card could include:

• The display name (or the name we see at Civitai)

• The filename (in case we change the filename in local)

• The type of resource (checkpoint, VAE, Lora, etc.)

• download URL

• Hash

• Upload date

• version (some models have different "versions" like "BakedVAE" or "NoVAE...) and numeric version (other models simply have more traditional numeric versions )

• model family (in civitai all versions of a model are under the same "family page". That.

• thumbnail URL or embedded thumbnail (maybe Civitai doesn't want to be feeding everybody's thumbnails from other programs, so it could be included in the file locally)

• Then specific type-related info, like recommended steps, scheduler, VAE and etcetera for checkpoints; or the trigger words for LORAs for example. Pretty much all the info you can find in the page of any model.

• And author's comments. As sometimes these comments are really valuable

For the implementation of the info card I suggest a json file attached to the end of the file (CAT command in linux) or another type of metadata structure. For the (optional, if not a simple URL) embedded thumbnail image I'm not sure. I know small images can be embedded in files but not sure how to do it in a safe way (if done in the "easy and fast way" that I have in mind, I can see how someone could use that for adding a virus or some other malware there.
Also the format, if not using JSON, should be modular/scalable as, more likely than not, it will be modified and extended in the future.

For better maintenance, the info card should be automatically updated and re-attach to the model file every time the author updates the model. So it should be a fully automated process that doesn't require any manual job on any side.

Overall at the end we will have a better model interoperability that will allow us to know what everything is and how to keep track of that. This could also eventually allow for other nice quality of life improvements: for example ComfyUI or Automatic1111 could detect the version of your checkpoints and check if there is a newer version of it automatically.