Code Implementation: Optimizing Directus Components with Merging and Prop Improvements

[Fritsch-Tech]

🔧 Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Codebase improvement
• Other (if none of the other choices apply)

🚨 Checklist

• I've read the guidelines for contributing
• I've added necessary documentation (if appropriate)
• I've ensured that my code additions do not fail linting or unit tests (if applicable)
  Title: "Code Implementation: Optimizing Directus Components with Merging and Prop Improvements"

Description

This pull request implements the proposal discussed in discussion #370 .

The following changes have been made:

1. Merging Directus Components: DirectusAsset and DirectusImage components have been merged into a single DirectusFiles component. This consolidation aims to improve code organization and maintainability.

2. Prop Improvements: To simplify transformations, I have introduced a new Directus Transformation prop that accepts either a preset or a custom transformation (of type string | CustomTransformations). I also added the filname prop. We are now on par with the directus API.

I believe these changes maintain full backward compatibility, but I would like to seek your opinion before proceeding. Before merging, test cases will need to be written and thoroughly evaluated to ensure the changes function as expected.

Please review the changes and provide your valuable feedback.

Thank you for considering this pull request, and I look forward to your input before proceeding further!

😊