openpilot 0.11.2 release

## release checklist

### Go to staging
- [x] make a GitHub issue to track release with this checklist
- [ ] create release master branch
- [x] create a branch from upstream master named `zeroeleventwo` for release `v0.11.2`
- [x] revert risky commits (double check with autonomy team)
- [x] push the new branch
- [x] push to staging:
- [x] make sure you are on the newly created release master branch (`zeroeleventwo`)
- [x] run `BRANCH=devel-staging tools/release/build_stripped.sh`. Jenkins will then automatically build staging on device, run `test_onroad` and update the staging branch
- [ ] bump version on master: `openpilot/common/version.h` and `RELEASES.md`
- [ ] post on Discord, tag `@release crew`

### Go to release
- [ ] before going to release, test the following:
- [ ] update from previous release -> new release
- [ ] update from new release -> previous release
- [ ] fresh install with `openpilot-test.comma.ai`
- [ ] drive on fresh install
- [ ] no submodules or LFS
- [ ] check sentry, MTBF, etc.
- [ ] stress test passes in production
- [ ] publish the blog post
- [ ] `git reset --hard origin/release-mici-staging`
- [ ] tag the release: `git tag v0.11.2 && git push origin v0.11.2`
- [ ] create GitHub release
- [ ] final test install on `openpilot.comma.ai`
- [ ] update factory provisioning
- [ ] close out milestone and issue
- [ ] post on Discord, X, etc.

Start by reviewing the release checklist in this issue and the release procedures it references, including `openpilot/common/version.h`, `RELEASES.md`, and `tools/release/build_stripped.sh`. This tracks a full release, with staging and production validation, publishing, tagging, and factory provisioning; it is coordination work rather than a self-contained newcomer change.

Written by the indexing model from the issue text.