Images break object promotion

[finbargiusti]

Prerequisites

• I am using the latest stable release of Neovim
• I am using the latest version of the plugin

Neovim Version

NVIM v0.10.4 Build type: Release LuaJIT 2.1.1736781742

Neorg setup

load = {
    ["core.defaults"] = {},
    ["core.keybinds"] = {
        config = {
            default_keybinds = false,
        }
    },
    ["core.dirman"] = {
        config = {
            use_popup = false,
            workspaces = workspaces,
            default_workspace = "notes",
            index = 'index.norg'
        },
    },
    ["core.dirman.utils"] = {},
    ["core.integrations.treesitter"] = {},
    ["core.highlights"] = {},
    ["core.integrations.image"] = {
        config = {
        }
    },
    ["core.latex.renderer"] = {
        config = {
            conceal = true,
            render_on_enter = false,
            debounce_ms = 2000,
            min_length=3
        }
    },
    ["core.concealer"] = {},
    ["core.completion"] = {
        config = {
            engine = "nvim-cmp"
        },
    },
    ["core.summary"] = {
        config = {
            strategy = "default"
        }
    }
}

Actual behavior

When using (neorg.promo.promote.nested) on a block that contains a
.image macro, nothing happens.

Expected behavior

The block should be promoted recursively, regardless of the image

Steps to reproduce

Have some local image and use the following norg file:

* Heading
  
   Some text

  .image ./path/to/image.png

Then, highlighting over the heading, attempt to promote using a keybind to the above mapping.

Potentially conflicting plugins

For images, I'm using the neorg integration for 3rd/image.nvim

Other information

No response

Help

Yes, but I don't know how to start. I would need guidance (check question below)

Implementation help

I'm new to this project, and I like it a lot! And I'm willing to contribute to fix this bug, but I'd like to know where to start. I know where to find the code for promo, but I'm not quite sure how the .image macro is actually handled internally, so some code pointers would help!

[finbargiusti]

As a note, maybe it would be best to merge that .image macro into the preexisting @image tag?
For example, one could add an optional parameter after @image that passes the path
to the local file.