Release framework crates v0.3.2

[madsmtm]

Blocked on #792, and I probably also want to mark AppKit as safe (EDIT: Done in ad2767b).

This only releases the framework crates, the changes in objc2 do not affect these. I will work towards a objc2 v0.7.0 with small breaking changes, but the framework crates should be compatible with this too, they have a dependency on it of >=0.6.2, <0.8.0, and I will make sure that the breaking changes in objc2 do not affect the framework crates.

Checklist:

• The branch is named ci-full, such that the full CI will run.
  • I have fixed everything apart from the autogenerated framework tests, that probably needs us to run CI on macOS 26.
• Changelogs have only been modified under the Unreleased header.
  • Yes, apart from 1bed725.
• Tests have been run on macOS 10.12.
• Tests have been run on macOS 10.12 32bit.
• Run cargo semver-checks --default-features.
  • The breakage is all from Xcode 26 in Update to Xcode 26.0 #762 or from adding #[repr(packed)] in 191b5bf, and is documented in the changelog.

Post merge:

• Run cargo release --exclude block2 --exclude dispatch2 --exclude objc2 --exclude objc2-encode --exclude objc2-exception-helper --exclude objc2-proc-macros.

[madsmtm]

Damn, I ran into rust-lang/rust#138907, see e.g. the docs build for objc2-core-foundation. I thought I'd avoided it, but the problem is that it still pulls in the old objc2 which I haven't yet released a fix with.

[madsmtm]

I've released objc2 v0.6.3 and block2 v0.6.2, and triggering a rebuild of objc2-core-foundation seemed to fix it:
https://docs.rs/crate/objc2-core-foundation/0.3.2/builds/2557992

[madsmtm]

I have triggered a rebuild of the crates that failed docs, and am now continuing the release

[madsmtm]

And everything has been released! 🎉

Still need to monitor the docs builds, but it'll take docs.rs a while to finish building all the crates, see their queue.

EDIT: Seems like they all built correctly.