Help prevent accidental commit of version specific files

When opening an existing project in a new version, Unity will modify at least `ProjectVersion.txt` and `manifest.json` (and probably `packages-lock.json`. If the user did not plan on changing the version, it is very easy to commit a version upgrade by mistake.

Can the Rider Unity support help here? Perhaps create a new change list just for these version updates?

The downside is what if the user meant to update? It's now easy to overlook the version update when committing other changes. What if the version update also rewrites assets? Now the updated assets and the saved version number are in separate change lists.

Perhaps a simple commit check would be best - show a confirmation prompt if `ProjectVersion.txt` is modified?

Start by reviewing how Rider Unity support handles changes to ProjectVersion.txt, manifest.json, and packages-lock.json, and where commit checks or change lists are integrated. The issue presents separate change-list and confirmation-prompt options without choosing one, so the intended behavior and completion criteria need to be clarified before implementation.

Written by the indexing model from the issue text.