Dirty check fails after Cocoa version bump

[jamescrosswell]

We have a chore(deps) PR that bumps the CocoaSDK from v8.10.0 to v8.11.0.

It looks like although this bumps the CocoaSDK, it hasn't recompiled our bindings and committed the updated version of these to source (which is why the dirty check is failing when CI runs the build on this PR).

I'm not sure how the chore(deps) PRs get created (presumably by some kind of bot) but however it happens, we need to tweak the process so that it not only bumps the version of the Sentry Cocoa module we depend on but also rebuilds our bindings and commits any changes to thes as part of the same PR, each time we upgrade this module.