Add missing information into event ResourceDeleted

[bartlomiejmarszal]

PR Description: Add Resource Type to ResourceDeleted Event

Summary

This pull request introduces a new feature to the ResourceDeleted event by adding a resourceType property. This enhancement allows for more detailed event handling by specifying the type of resource that has been deleted.

Key Changes

• ResourceDeleted Class:

  • Added a private property resourceType to store the type of the resource.
  • Implemented setResourceType and getResourceType methods to manage the resourceType property.
  • Updated the jsonSerialize method to include the resourceType in the serialized data.

• ResourceRepository Class:

  • Extracted the resource type using $resource->getTypes() and set it in the ResourceDeleted event using the new setResourceType method.

Benefits

• Enhanced Event Data: By including the resource type in the ResourceDeleted event, consumers of the event can make more informed decisions based on the type of resource that was deleted.
• Improved Code Clarity: The changes make the event handling more explicit and easier to understand by clearly defining the type of resource involved in the deletion.

Notes

• This change assumes that the resource type is always available and that the first type in the list is the primary type to be used. Further validation or error handling may be required if this assumption does not hold in all cases.

[Karol-Stelmaczonek]

• New code is covered by tests (if applicable)
• Tests are running successfully (old and new ones) on my local machine (if applicable)
• New code is respecting code style rules
• New code is respecting best practices
• New code is not subject to concurrency issues (if applicable)
• Feature is working correctly on my local machine (if applicable)
• Acceptance criteria are respected
• Pull request title and description are meaningful

[tikhanovichA]

Unit tests please

[tikhanovichA]

Review Checklist

• New code is covered by tests (if applicable)
• Tests are running successfully (old and new ones) on my local machine (if applicable)
• New code is respecting code style rules
• New code is respecting best practices
• New code is not subject to concurrency issues (if applicable)
• Feature is working correctly on my local machine (if applicable)
• Acceptance criteria are respected
• Pull request title and description are meaningful
• Pull request's target is not master
• Commits are following conventional commits
• Commits messages are meaningful
• Commits are atomic
• Changelog is updated according to changes (if applicable)
• Documentation is updated according to changes (if applicable)

[tikhanovichA]

@bartlomiejmarszal could you please check unit tests?

[github-actions]

Version

Target Version	16.1.0
Last version	16.0.2

There are 0 BREAKING CHANGE, 1 feature, 4 fixes