refactor(frontend): update deleteDialog logic

[yassinedorbozgithub]

Motivation

The main motivation of this PR is to refactor delete useDialog, delete component and to introduce the new callbackHandler.

Fixes #587

Screenshots

Type of change:

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• I have performed a self-review of my own code
• New and existing unit tests pass locally with my changes

[marrouchi]

I'm thinking about refactoring even more. Maybe we can have a single useDelete() that accepts an array of ids. Within the useMutation() it would decide to call either bulk delete or just delete. Let me know what you think.

[yassinedorbozgithub]

I'm thinking about refactoring even more. Maybe we can have a single useDelete() that accepts an array of ids. Within the useMutation() it would decide to call either bulk delete or just delete. Let me know what you think.

It make a full sense, it's a good idea, happy to implement those enhancements 🚀

[IkbelTalebHssan]

LGTM ✔️ 🚀

[marrouchi]

Suggested change

	onDeleteError = () => {},
	onDeleteSuccess = () => {},
	onError = () => {},
	onSuccess = () => {},

Since it's the delete dialog, it's kindof repetitive to indicate it again.

[yassinedorbozgithub]

The main motivation of this naming is to avoid overriding the onError attribute of the dialog component

[yassinedorbozgithub]

Closed in favor of using useDialogs hook
Implementation example : #662