Oh also exposes the Access settings since I thought that was useful.

So the roadmap vaguely mentions "add all lfs.* git config keys to git lfs env output". I'd love some automated way to do this, so we don't have to update it every time we add a new property.

However, I think this PR shows why the manual approach is good:

1. We output the value that Git LFS is using. It may come from an env var, a git config value, or implicit default in the tool.
2. The tests have to be updated with all the new properties. I'd be open to another solution to this if you have any thoughts though. Definitely not a blocker for this PR.

🚢

Although we could dump the contents of the git config fairly easily, it doesn't totally reflect how we use the values internally (defaults, derived values) so I kinda like the hand crafted approach. Could maybe use reflection to automate if it became a problem? Otherwise I think this is ok for now.