Sanity does not sync to changes in image attributes (Metadata)

[Brettkgamble]

Describe the bug
This may be a feature request as I am sure the plug-in works as intended.

When an assets metadata is updated in Cloudinary, Sanity does not update with the changes.

A clear and concise description of what the bug is.
To work around this issue the user must remove the image and re-add, then re-publish. This is fine as a part of a simple workflow (one image in one document), but when an image appears in multiple documents it becomes very difficult to even find which documents require this remove/add update.

To Reproduce

Steps to reproduce the behavior:

1. Select an image in your document using the plugin.
2. Publish the document
3. Go back into Cloudinary and update some metadata, title for example, or structured metadata.
4. Sanity does not update the asset with the changed data
5. In the document, remove the asset
6. Re-add the asset and publish
7. The asset now has the changes/additional data available.

I like this plug-in, and see a problem with workflow (and am happy for any workarounds to this). We have our logo appearing in literally thousands of documents so performing this kind of update is not feasible. The only alternative is to fall back on Sanity's media assets which can be structured with what ever content we like, but then we miss out on all of the advantages that Cloudinary provides such as transformations, storage, etc

Expected behavior
The plugin hooks into changes made to the asset in Cloudinary.

[frodeste]

Can we at least get the metadata in? As of now, I do not see the metadata:

export type CloudinaryAsset = {
  _type: "cloudinary.asset";
  public_id?: string;
  resource_type?: string;
  type?: string;
  format?: string;
  version?: number;
  url?: string;
  secure_url?: string;
  width?: number;
  height?: number;
  bytes?: number;
  duration?: number;
  tags?: Array<string>;
  created_at?: string;
  derived?: Array<
    {
      _key: string;
    } & CloudinaryAssetDerived
  >;
  access_mode?: string;
  context?: CloudinaryAssetContext;
};