Bumps [sorbet-runtime](https://github.com/sorbet/sorbet) from 0.5.5883 to 0.5.5888.
- [Release notes](https://github.com/sorbet/sorbet/releases)
- [Commits](https://github.com/sorbet/sorbet/commits

)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

build(deps): bump sorbet from 0.5.5883 to 0.5.5888 in /Library/Homebrew

Bumps [sorbet](https://github.com/sorbet/sorbet) from 0.5.5883 to 0.5.5888.
- [Release notes](https://github.com/sorbet/sorbet/releases)
- [Commits](https://github.com/sorbet/sorbet/commits

)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Adjust RuboCop formatter on CI.

Fix reading HOMEBREW_LIVECHECK_WATCHLIST file

formula: rename `installed_prefix` and `opt_or_installed_prefix_keg`

Use `Homebrew::Style` for `brew cask style`.

build(deps): bump rubocop from 0.89.1 to 0.90.0 in /Library/Homebrew

CPU: add ability to check for Rosetta

When running within an Intel terminal, `uname -m` and friends return Intel-based
values for compatibility. An Intel shell will also prefer to launch Intel slices of
programs unless the program is ARM-only.

It's an open question how Homebrew should manage running in Intel mode. Should it
continue to behave as though the Mac is Intel-based, like it does now? Should it
recognize it's ARM-based? Either way, it's useful for us to be able to tell whether
the Mac is running under Rosetta or whether it's a real Intel Mac.

Bumps [rubocop](https://github.com/rubocop-hq/rubocop) from 0.89.1 to 0.90.0.
- [Release notes](https://github.com/rubocop-hq/rubocop/releases)
- [Changelog](https://github.com/rubocop-hq/rubocop/blob/master/CHANGELOG.md)
- [Commits](https://github.com/rubocop-hq/rubocop/compare/v0.89.1...v0.90.0

)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

dev-cmd/audit: whitelist clang-format@8 to be non-keg-only

Remove need for separate `.rubocop_cask.yml`.

Don't allow platform in cask descriptions.

docs: The maintainer monthly call has a Slackbot now

os/linux: add more Xcode stubs.

- Adding and removing people from the calendar invite was a burden. So we rely on Slack reminders.

Co-authored-by: Mike McQuaid <mike@mikemcquaid.com>

Saw these on a random user report.