Use unencoded names for selectors to improve Xcode test reports

[bnickel]

This idea is a little half baked but, a selector can be any finite UTF-8-encodable string, so why do we need to call c99ExtendedIdentifier? (Even : is meaningless to the runtime.)

If we omit it the transformation, the test sidebar and results views become a lot more readable:

We can also make the test console slightly prettier by overriding the undocumented nameForLegacyLogging property to omit the class name:

Test Suite 'Selected tests' started at 2022-09-02 14:11:13.591
Test Suite 'QuickTests.xctest' started at 2022-09-02 14:11:13.592
Test Suite 'FunctionalTests_ItSpec' started at 2022-09-02 14:11:13.593
Test Case 'has a description with セレクター名に使えない文字が入っている 👊💥' started.
Test Case 'has a description with セレクター名に使えない文字が入っている 👊💥' passed (0.002 seconds).
Test Suite 'FunctionalTests_ItSpec' passed at 2022-09-02 14:11:13.595.
	 Executed 1 test, with 0 failures (0 unexpected) in 0.002 (0.002) seconds
Test Suite 'QuickTests.xctest' passed at 2022-09-02 14:11:13.595.
	 Executed 1 test, with 0 failures (0 unexpected) in 0.002 (0.003) seconds
Test Suite 'Selected tests' passed at 2022-09-02 14:11:13.595.
	 Executed 1 test, with 0 failures (0 unexpected) in 0.002 (0.004) seconds
Program ended with exit code: 0

Checklist - While not every PR needs it, new features should consider this list:

• Does this have tests?
• Does this have documentation?
• Does this break the public API (Requires major version bump)?
• Is this a new feature (Requires minor version bump)?

[younata]

Thank you so much @bnickel! I took this and added it as part of the next version of Quick. Really appreciate the work and idea.