Git: core.gvfs config setting

[derrickstolee]

The core.gvfs config setting does a lot of things, including block unwanted commands.

This setting was dropped as part of the rename effort (#38) and should be put back for now.

However, there are a lot of things that config options does that we may not want it to do in the Scalar world. Update Git to split those actions apart based on other config options or add a core.scalar for our situation.

For example, we still want to block git gc, but that could be part of core.virtualizeobjects instead.

[github-actions]

Labeling this issue as stale. There has been no activity for 30 days. Remove stale label or comment or this issue will be closed in 7 days.

[github-actions]

Labeling this issue as stale. There has been no activity for 30 days. Remove stale label or comment or this issue will be closed in 7 days.

[derrickstolee]

I'm moving this issue to the EA milestone after talking with @wilbaker about it.

This is likely a blocker for merging the sparse-checkout feature branch into vfs-2.2x.0 since we likely do not want VFS for Git repos to run git sparse-checkout. Further, we may want things like the transport layer (#7, #36) to be a "scalar only" feature.

However, I don't see anything here blocking us from collecting the performance data we need for MVP. In fact, we likely won't want to merge the sparse-checkout feature branch into vfs-2.2x.0 until we have completed our performance investigation.