Added the ability to specify a maximum depth for CBOR decoding

[dimitribouniol]

Added the ability to specify a maximum depth for CBOR decoding. This addresses a crash reported in #92 that can occur when certain types of data causes the recursive nature of the decoder to escape the stack for the given thread. I do suggest we set a more reasonable default than .max, though that can break some user's workflows if they weren't expecting it, so maybe requires a new version? Food for thought 😅

[hamchapman]

Nice! I think what you've done here with exposing the option but setting the default value to Int.max is fine for now.

[dimitribouniol]

@hamchapman Could you cut a new release with this fix when you get a chance? Since crashes happened prior to this fix, I’d like to update the minimum version in https://github.com/swift-server/webauthn-swift and re-enable some fuzzing tests.

[hamchapman]

Yep, just tagged v0.4.7 and pushed a new version to Cocoapods

[hamchapman]

We might have to tweak the new test you added given the CI failure here: https://github.com/valpackett/SwiftCBOR/actions/runs/8451024581/job/23148461601

I assume the CI runner is relatively low powered and so hits an issue quicker than a typical machine would

[dimitribouniol]

Good catch! Let me make a new PR with a lower testing limit. It shouldn't impact code folks run though.

[dimitribouniol]

@hamchapman Lowered it here: #103. Can you re-run the CI a few times before merging to see if 512 is low enough? I don't have access to that particular button unfortunately.