Add test coverage for update-checkout --stash option

[MaxDesiatov]

update-checkout has a Python unit test suite at utils/update_checkout/tests. You can run it using utils/update_checkout/run_tests.py or lit + validation-test/Python/update_checkout.swift. The test suite is centered around an intermediary unittest.TestCase subclass from which all the effective test classes inherit. This base class is responsible for setting up and tearing down a mock-up environment consisting of a directory of local remotes and a source root — a directory for their clones. Subclasses define test functions that run update-checkout commands against these mock repositories and perform state checks.

I think a single test function that

1. clones the remotes using update-checkout
2. creates some untracked files in several clones
3. runs update-checkout with --stash
4. verifies that the untracked files have indeed been stashed and nothing else happened

would good enough for now (the update/clone tests, if any, are really basic anyway). I would place this function in a new subclass in its own file.

Originally posted by @AnthonyLatsis in #71178 (comment)

[fabricerenard12]

Hi MaxDesiatov, I am new to the open-source contribution. If no one is currently working on this issue, I would like to work on it. If that is the case, could you assign it to me? Thanks a lot!

[MaxDesiatov]

1. clones the remotes using update-checkout

My concern here is that this is quite a long-running operation for real repositories. Maybe creating some mock repositories on the file system in a temp directory could be a sufficient workaround for that.

[AnthonyLatsis]

1. clones the remotes using update-checkout

Using the mock remotes that are already set up for each test, of course. See test_clone.py.