Don't require mount setup for etag/mtime propagation.

To propagate etag and mtimes across storages, the filesystem code will load the mounts that are nested inside a folder (any depth) and use those mounts to calculate the etag/mtime of a folder.

Because of this, there are cases where we're doing a lot of work to setup the various mounts, to then only use them to fetch the root metadata.

Since the oc_mounts table records the fileid of the root of the mounts, we could instead use that to collect the fileid of the nested mounts we need, and fetch the data directly from the filecache, without having to setup the actual mounts.

Some considerations:

• When listing a directory, we need to ensure we only do this logic once for all relevant folders at once, not for every sub-folder individually.

Start by tracing the filesystem code that propagates etags and mtimes, including the oc_mounts table, nested mount roots, and filecache lookups. Check the directory-listing path to understand how relevant folders are processed together; done means root metadata is fetched without setting up unnecessary mounts and the logic runs once for a listing rather than once per sub-folder.