docs: improve FAQ entry about disabling snapshot.auto-track

[senekor]

• I have updated CHANGELOG.md
• I have updated the documentation (README.md, docs/, demos/)
• I have updated the config schema (cli/src/config-schema.json)
• I have added/updated tests to cover my changes

[josephlou5]

Just checking this out because I was curious and saw a couple things, but probably need review from someone else who knows better 🙃

[senekor]

Doh! Just saw there already is an entry about it... Let's see if there is any value to merging the two. Otherwise I will just close this PR.

[senekor]

So, the existing entry focuses on "scratch files". Meaning, I presume, files that are never intended to be tracked & committed. Maybe there could be some value in saying something for users that are actually trying to get back to the git workflow. In that case, users are adding new files that may end up being committed later, they just want to do that tracking explicitly.

And regarding the scratch files, it might be good to mention the workflow where people commit scratch files and squash it into a commit that lives parallel to any feature branches being worked on. A megamerge then brings all changes into the working copy.

[PhilipMetzger]

if you want to see some previous plus and minus points for auto-tracking just take the time to scroll through #323.

[senekor]

Yeah I started doing that and went back and forth with my ideas to improve the FAQ entry... I was a little trigger happy with opening the PR.