fix(services/fs): add content length and modified time to metadata

[mhambre]

Which issue does this PR close?

Closes #7187.

Rationale for this change

Explained in issue.

What changes are included in this PR?

Metadata is no longer defaulted and required data is saturated by the tokio::fs DirEntry's metadata.

Are there any user-facing changes?

N/A

AI Usage Statement

N/A

[jeevaprakashdr]

@matthambrecht I am new to the code base. I see this fix is simple. I am wondering if there is any way I can verify the changes.

[mhambre]

@matthambrecht I am new to the code base. I see this fix is simple. I am wondering if there is any way I can verify the changes.

If you go back to the original issue I posted a simple code snippet to verify that the changes work

[jeevaprakashdr]

@matthambrecht I am new to the code base. I see this fix is simple. I am wondering if there is any way I can verify the changes.

If you go back to the original issue I posted a simple code snippet to verify that the changes work

Got the following from the code snipped mentioned in the issue.

Metadata {
    mode: DIR,
    is_current: None,
    is_deleted: false,
    cache_control: None,
    content_disposition: None,
    content_length: Some(
        128,
    ),
    content_md5: None,
    content_range: None,
    content_type: None,
    content_encoding: None,
    etag: None,
    last_modified: Some(
        Timestamp(
            2026-02-18T13:57:31.558337789Z,
        ),
    ),
    version: None,
    user_metadata: None,
}

For a empty directory content_length set to Some(128) I am unsure if this needs explicitly state in KB or MB

[Xuanwo]

Thank you for working on this!