Make sure Leave event is emitted on internal deletions of fabrics

[tcarmelveilleux]

Problem

The Basic Info cluster Leave event is required to be generated when a fabric is removed. It is not certain this is generated in every instance of fabric removal.

Proposed Solution

• Audit all paths of fabric removal to ensure Leave event is generated.

[Damian-Nordic]

@tcarmelveilleux Note that after e5e09f5c00 Leave event is no longer generated because ACLs are removed first and then generating a report fails with UNSUPPORTED_ACCESS error. I onced fixed it by moving this part to operational-credentials-server.cpp to have a better control over the order of the operation (see #18434), but maybe we should do the other way around. The point is to execute all the actions in a single listener because otherwise it's very easy to break things by changing order of initialization of certain components.

[bzbarsky-apple]

#21012 tracks the ordering issue there.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[bzbarsky-apple]

We now generate Leave events in FabricWillBeRemoved, which is a notification from the fabric table. So any fabric removal that the fabric table knows about will generate the event.

@tcarmelveilleux Are you worried about fabric removals directly from storage, bypassing the fabric table?