Subscription "delete-relationship" is not triggered by nested delete operations.

[MacondoExpress]

Describe the bug
As for the title, subscription "delete_relationship" events are not triggered by the nested delete operations.

Type definitions

 type Actor {
    id: ID!
    movies: [Movie!]! @relationship(type: "ACTED_IN", direction: OUT)
}

type Movie {
    id: ID!
    actors: [Actor!]! @relationship(type: "ACTED_IN", direction: IN)
    workers: [Worker!]! @relationship(type: "WORKED_IN", direction: IN)
}

type Worker {
    id: ID!
    favoriteActors: [Actor!]! @relationship(type: "FAV", direction: OUT)
}

To Reproduce

Use the following dataset:

CREATE (a:Movie { id: "1" })
CREATE (b:Movie { id: "2" })
CREATE (a)<-[:ACTED_IN]-(c:Actor { id: "5" })
CREATE (b)<-[:WORKED_IN]-(d:Worker { id: "6" })
CREATE (c)<-[:FAV]-(d)

Expected behavior
With the following mutation:

mutation {
    deleteMovies(where: { id: "2" }, delete: { workers: {} })  {
        nodesDeleted
    }
}

I received 3 events:

[
  {
    "id": 1,
    "typename": "Movie",
    "timestamp": 1705608145930,
    "event": "delete",
    "properties": {
      "old": {
        "id": "2"
      },
      "new": undefined
    }
  },
  {
    "id": 3,
    "typename": "Worker",
    "timestamp": 1705608145930,
    "event": "delete",
    "properties": {
      "old": {
        "id": "6"
      },
      "new": undefined
    }
  },
  {
    "id": 1,
    "id_from": 3,
    "id_to": 1,
    "relationshipName": "WORKED_IN",
    "fromTypename": "Worker",
    "toTypename": "Movie",
    "timestamp": 1705608145930,
    "event": "delete_relationship",
    "properties": {
      "from": {
        "id": "6"
      },
      "to": {
        "id": "2"
      },
      "relationship": {}
    }
  }
]

As visible by the events received, there is no event about the deleted relationship FAV.

[neo4j-team-graphql]

Many thanks for raising this bug report @MacondoExpress. 🐛 We will now attempt to reproduce the bug based on the steps you have provided.

Please ensure that you've provided the necessary information for a minimal reproduction, including but not limited to:

• Type definitions
• Resolvers
• Query and/or Mutation (or multiple) needed to reproduce

If you have a support agreement with Neo4j, please link this GitHub issue to a new or existing Zendesk ticket.

Thanks again! 🙏

[neo4j-team-graphql]

We've been able to confirm this bug using the steps to reproduce that you provided - many thanks @MacondoExpress! 🙏 We will now prioritise the bug and address it appropriately.