Rename this test because another test by the same name already exists:
reverse-execution/TestReverseContinueNotSupported.py.
Having multiple tests of the same name breaks running any test with:
`lldb-dotest -p <TestName>`.
This tests reverse continue _commands_, and so the rename adds
"Commands" to the test name (TestReverseContinueCommandNotSupported.py)
The new test added in https://github.com/llvm/llvm-project/pull/132783
was failing on Windows because it created a new error to say it did not
support the feature, but then returned the existing, default constructed
error. Which was a success value.
This also changes the GDBRemote error message to the same phrasing used
in all the other places so we don't have to special case any platform.
This introduces the options "-F/--forward" and "-R/--reverse" to
`process continue`.
These only work if you're running with a gdbserver backend that supports
reverse execution, such as rr. For testing we rely on the fake
reverse-execution functionality in `lldbreverse.py`.
