Add support for Xcode Runtime issue breakpoints

[zenangst]

Short description 📝

This PR adds support for Xcode runtime issues breakpoints. It simply adds a new case to the BreakpointExtensionID called .runtimeException which can be used to generate breakpoints.

Solution 📦

Add missing case to BreakpointExtensionID for generating runtime issue breakpoints.

Implementation 👩‍💻👨‍💻

• [x] Adds new BreakpointExtensionID case to support runtime issue breakpoints
• [x] Expands the XCBreakpointListTests to include looking for the runtime exception
• [x] Update the breakpoints fixture to include a runtime issue breakpoint

[kwridan]

@all-contributors add @zenangst for code

[allcontributors[bot]]

@kwridan

I've put up a pull request to add @zenangst! :tada:

[zenangst]

Found a nasty little casing issue which caused the tests to not compile. Fixed here https://github.com/tuist/XcodeProj/pull/761/commits/ad3d477b665f47e185417279f6e027f1e0cb26f3

[zenangst]

I bit unsure what is going on with the test_read_write_produces_no_diff test.

[zenangst]

@kwridan I tried something really quickly but I ended up with the clash between using CaseIterable and having an associated type on the enum. They don't really work well together.

I think to really nails this, I'll open an issue, so that the rest of the community can also chip in an spitball some ideas, like you suggested.

I pushed a commit to improve on the naming.

[zenangst]

Made an issue here - https://github.com/tuist/XcodeProj/issues/763

[kwridan]

Awesome thanks @zenangst 🙏

[pepicrft]

Thanks for tackling this one @zenangst. I'll go ahead with merging this and I'll tackle your issue separately.