Bug: treeView doesn't return trees with null url

**Description**: When querying a tree listing, the treeViewFast will return trees with the `git_repository_branch`, `git_repository_url`, `commit_hash` and `commit_name` nulls, while the treeView doesn't return such rows.

**Reproduction**: Execute the queries for the [treeListingFast](https://github.com/kernelci/dashboard/blob/b7b8a028e3adcb389df9ecbb752ad0d21875bec8/backend/kernelCI_app/queries/tree.py#L209) and [treeListing](https://github.com/kernelci/dashboard/blob/b7b8a028e3adcb389df9ecbb752ad0d21875bec8/backend/kernelCI_app/queries/tree.py#L96) and substituite the date conditions by `DATE(start_time) = '2025-04-16'`, origin by `redhat` and no need for the counts. You should see one row with null fields in the fast query, but none in the other query.

Start with backend/kernelCI_app/queries/tree.py, comparing treeListingFast at line 209 with treeListing at line 96. Run both queries using DATE(start_time) = '2025-04-16' and origin redhat, without counts, then trace why the row with null repository and commit fields is omitted. Done means treeListing returns the same applicable row as treeListingFast.

Written by the indexing model from the issue text.