## 🚀 Release Update: `mediaContent.mjs` Enhancements & Optimizations

We have released a significant update to `mediaContent.mjs`, focusing on memory management, and improved data control. 📦

### 🔍 New Feature: Raw Data Access
We have introduced a new property within the `MediaContentMetadata` structure to provide more transparency.

* **`valFetchMediaContent` Function:** The new function added.
* **`_fetchData` Property:** This new property provides direct access to the **original, raw value** retrieved by `parseFile`. 
* **⚠️ Developer Responsibility:** Please note that `_fetchData` is **pure and unvalidated**. Because it bypasses our standard validation pipeline, it is the developer's responsibility to implement custom validation logic if these native values are used.
* **⚙️ Customization:** If you want `_fetchData` to return `null`, you can achieve this via `parseMediaMetadata` by passing `null` to the `metadata` argument (manual metadata overrides automatic extraction). 🔄

### ⚡ Performance & Memory Optimizations
We have refined the internal data structure of `MediaContent` to ensure higher efficiency. 🚀

* **Reduced Memory Footprint:** The `MediaContent` jsDoc no longer utilizes `null` values. Additionally, fields without data are marked as `undefined`.
* **Optimized Data Transfer:** These changes significantly reduce the volume of data held in memory and decrease the payload size when exporting or importing data for classes that utilize `MediaContent`. 📉

### ⚠️ Breaking Changes & Removals
To maintain a clean and efficient API, some redundant functions have been removed. 🛠️

* **Removed Functions:** `getMediaContentMetadata` and `valMediaContentMetadataPartial` have been officially removed. These functions are now obsolete due to the architectural improvements in the latest version of `MediaContent`.