Missing owner property on Worlds deployment

**Describe the bug**
We are not including the `owner` property on the deployment files included while deploying a world to the World Content Server.

This property should be included in the metadata file of the entity:
```
[
{
"id": "bafkreifmwy2oomjbt4wn62c5u7zix2wpjww5ie7x5gvliwwub7lwrtqy7e",
"timestamp": 1757438805711,
"version": "v3",
"type": "scene",
"pointers": [
...
],
"content": [
...
],
"metadata": {
"allowedMediaHostnames": [],
"owner": "0xa7cdf25a0211c089a0338c0e5b204a34ac180489", # <-- This value
"main": "bin/index.js",
...
}
}
]
```

**To Reproduce**
Steps to reproduce the behavior:

1. Deploy a world through the CH
2. Get World Entity ID by calling POST `/entities/active` endpoint:
```
curl --location 'https://worlds-content-server.decentraland.org/entities/active' \
--header 'Content-Type: application/json' \
--data '{
"pointers": ["dafu.dcl.eth"]
}'
```
3. Grab the entity ID and pulls its content file:
```
curl --location 'https://worlds-content-server.decentraland.org/contents/bafkreifmwy2oomjbt4wn62c5u7zix2wpjww5ie7x5gvliwwub7lwrtqy7e'
```
4. Check that the JSON received after pulling that content has no owner `metadata.owner === ""`

**Expected behavior**
When deploying a world through the Web Builder using the same steps, the owner property is correctly set. Meaning that if we request the file of the World's Entity ID we will see that `metadata.owner` property has the correct value.

**Screenshots**
N/A

**Additional context**
We should populate the `metadata.owner` property the same way the Web Builder is currently doing. We will add a validation in the World Content Server to prevent this from happening again in the future.