Bumps [parallel_tests](https://github.com/grosser/parallel_tests) from 2.22.1 to 2.23.0.
- [Release notes](https://github.com/grosser/parallel_tests/releases)
- [Commits](https://github.com/grosser/parallel_tests/compare/v2.22.1...v2.23.0

)

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

Quarantine is available ONLY if the script exits with '2'.
It is definitely NOT available if Swift doesn't exist or if
it exits with '5' (incompatible SDK). All other cases are
from now on treated as unsupported.

Also print to standard error only when explictly required (via an
exception).

- backports to 3.11.4
- plist to 3.4.0

Rather than having to manually keep track of what version each thing in
here is and copy files around by hand on update let's use Bundler's
standalone mode and careful use of `.gitignore` to help us do it.

This means a `bundle update --standalone` will allow us to update all
gems in vendor.

We could consider vendoring other gems this way in future but I'd
suggest only doing this for gems with no dependencies or at least gems
with no native extensions. The only gem this applies to that we
currently use is `ruby-prof` and I'm not convinced it's widely used
enough to warrant vendoring for everyone. Perhaps that's another
criteria: it should be functionality that's used by non-developer
commands and/or normal Homebrew usage.

This speeds up execution by 3x on my machine and the script is simple
enough to warrant this.

Don't strip the : from root_url when using --keep-old.
Closes #4554.

After upgrading existing kegs, we now search and upgrade their
dependents as well. If any are detected that have broken linkage, they
are reinstalled from source.

If there are any formulae in the dependents tree that are pinned, they
are only reinstalled if they're not outdated; in all cases, a suitable
message is printed detailing the kegs that will be acted upon.

This increases the messages.rb unit test coverage to 100%.

Bumps [ruby-progressbar](https://github.com/jfelchner/ruby-progressbar) from 1.9.0 to 1.10.0.
- [Release notes](https://github.com/jfelchner/ruby-progressbar/releases)
- [Changelog](https://github.com/jfelchner/ruby-progressbar/blob/master/CHANGELOG.md)
- [Commits](https://github.com/jfelchner/ruby-progressbar/compare/releases/v1.9.0...releases/v1.10.0

)

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

Bumps [parser](https://github.com/whitequark/parser) from 2.5.1.0 to 2.5.1.2.
- [Release notes](https://github.com/whitequark/parser/releases)
- [Changelog](https://github.com/whitequark/parser/blob/master/CHANGELOG.md)
- [Commits](https://github.com/whitequark/parser/compare/v2.5.1.0...v2.5.1.2

)

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

Bumps [rspec-expectations](https://github.com/rspec/rspec-expectations) from 3.8.0 to 3.8.1.
- [Release notes](https://github.com/rspec/rspec-expectations/releases)
- [Changelog](https://github.com/rspec/rspec-expectations/blob/master/Changelog.md)
- [Commits](https://github.com/rspec/rspec-expectations/compare/v3.8.0...v3.8.1

)

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

Bumps [docile](https://github.com/ms-ati/docile) from 1.3.0 to 1.3.1.
- [Release notes](https://github.com/ms-ati/docile/releases)
- [Changelog](https://github.com/ms-ati/docile/blob/master/HISTORY.md)
- [Commits](https://github.com/ms-ati/docile/compare/v1.3.0...v1.3.1

)

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

brew test-bot --ci-upload is run on a Linux machine.
The macOS bottles have a prefix of "/usr/local".
The default prefix on Linux is /home/linuxbrew/.linuxbrew.
Elide prefix "/usr/local" in the bottle block, even it does not match
the default prefix. Ditto for cellar.

The default prefix is /usr/local on macOS
and /home/linuxbrew/.linuxbrew on Linux.

Fixes #4867

Ruby chmod follows symlinks, which can point to non-existent files. This
should fix quarantining Casks e.g. disk-inventory-x.

Gatekeeper's Path Randomization is currently making automated
installation a nightmare. Let's manually toggle the (undocumented) app
translocation bit in the `com.apple.quarantine` extended attribute.

While we're at it, let's also toss in some fixes:

- zip downloads with improper permissions that prevent us from
quarantining
- quarantine/release/skip downloads as requested by the user

This isn't the case on our CI for now.