🐛 Bug Report: VCS deployment sourceSize reports the whole cloned repo (.git included), inflating totalSize and deployments-storage metrics

### 👟 Reproduction steps 1. Self-hosted Appwrite `2.0.0`, PostgreSQL. Any Git-connected function whose `providerRootDirectory` is a subfolder of a repository (a monorepo makes this obvious, but any repo shows it). 2. Push a commit and let the VCS build run. 3. Look at the deployment in the Console, or `GET /v1/functions/{id}/deployments`. Observed on a repo with 19 Git-connected functions, each with its own `providerRootDirectory`: ``` function root dir sourceSize buildSize contact-email appwrite-functions/contact-email 4.33 MB 2.49 MB document-parser appwrite-functions/document-parser 4.33 MB 2.43 MB motive-sync appwrite-functions/motive-sync 4.33 MB 2.94 MB ifta-report appwrite-functions/ifta-report 4.33 MB 3.01 MB arrival-nudger appwrite-functions/arrival-nudger 4.33 MB 2.89 MB … all 19 … 4.33 MB (varies) ``` `sourceSize` is **byte-identical across every function**, regardless of root directory or how much code the function contains. It equals the size of the **whole repository**: `git ls-files -z | xargs -0 tar czf -` on the same commit is 4.46 MB. The same function deployed manually (a tarball of just that folder) reports `sourceSize` **0.07 MB**, and produces a **functionally identical build** — 2.86 MB vs 2.89 MB. ### 👍 Expected behavior `sourceSize` should describe that deployment's source — the content under `providerRootDirectory` that was actually built — as it did in 1.9.x, and as the manual-upload path still does. ### 👎 Actual behavior For VCS deployments, `sourceSize` is the size of the temporary clone directory, which is dominated by `.git`. `git fetch --depth=1` downloads every blob of the commit's tree into the object store; `core.sparseCheckout` only limits which files are written to the working tree. So th…