The version module exposed an optional git *GitRepository constructor argument, but the official build paths do not pass it. Prod traces show calls to dag.Version() receiving the contextual gitParent and inputs arguments only; the module then derives its private GitRepository from gitParent.Directory(".git").AsGit() when possible.

Keeping the public git argument made the versioning model look like it was already driven by a full contextual GitRepository. In practice, that path was dead for engine-dev, cli-dev, and release callers, and it obscured the real inputs that need to be replaced by Workspace.git().

Remove the public constructor argument while preserving the private GitRepository field and the existing gitParent-derived behavior. Regenerate the version module wrapper and dependent generated clients so the removed argument no longer appears in the module API.

Signed-off-by: Solomon Hykes <solomon@dagger.io>

The version module used a contextual inputs Directory to compute dirty dev
version digests. That input set had to maintain its own large ignore filter,
separate from the real build inputs. In practice that made the digest contract
fragile: every build-input change also required remembering to update a second
filter in the version module.

Remove the inputs argument and base dirty state on git instead. When local git
metadata is available, dirty detection now uses GitRepository.Uncommitted and
dirty dev digests use the digest of Uncommitted.AsPatch with metadata excluded.
This keeps the digest tied to the actual uncommitted patch instead of a
manually-maintained source snapshot.

Add a small internal workspaceGit shim to isolate the module from the current
GitRepository plumbing. The shim deliberately represents only local workspace
git state: HEAD, branches for the legacy ImageTag path, uncommitted changes,
the current semver tag, and the latest semver tag. This mirrors the shape we
want from a future core Workspace.git API, so swapping the implementation later
should be localized to the shim.

Linked git worktrees are still a current limitation because the contextual
gitParent input exposes .git as a file, not a directory. Preserve working dev
builds for that case with an explicit Version-level fallback: when local git
cannot be loaded, compute the next patch baseline from the upstream Dagger repo
tags and emit a digestless dirty dev version like vX.Y.Z-<timestamp>-dev. Keep
that fallback outside workspaceGit so the shim does not silently pretend that a
hardcoded upstream repository is workspace state.

Regenerate the version module bindings and the generated clients in cli-dev,
engine-dev, and release so the removed inputs constructor argument is reflected
in dependent modules.

Signed-off-by: Solomon Hykes <solomon@dagger.io>

Signed-off-by: Solomon Hykes <solomon@dagger.io>