create: add --go-mod option

build: bump minitest from 5.11.3 to 5.12.0 in /Library/Homebrew

Bumps [minitest](https://github.com/seattlerb/minitest) from 5.11.3 to 5.12.0.
- [Release notes](https://github.com/seattlerb/minitest/releases)
- [Changelog](https://github.com/seattlerb/minitest/blob/master/History.rdoc)
- [Commits](https://github.com/seattlerb/minitest/compare/v5.11.3...v5.12.0

)

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

build: bump minitest from 5.11.3 to 5.12.0 in /docs

Bumps [minitest](https://github.com/seattlerb/minitest) from 5.11.3 to 5.12.0.
- [Release notes](https://github.com/seattlerb/minitest/releases)
- [Changelog](https://github.com/seattlerb/minitest/blob/master/History.rdoc)
- [Commits](https://github.com/seattlerb/minitest/compare/v5.11.3...v5.12.0

)

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

Check blacklisted Casks when auditing.

More Homebrew/linuxbrew-core maintainer guide sections

Revert "formula_installer: don't always install test deps."

cleanup: some speedup optimisations.

- avoid calling `rm_ds_store` multiple times when unnecessary
- use native Ruby method to remove `.DS_Store` files as it saves
  shelling out to `find` and is a bit quicker.

formula_installer: don't always install test deps.

Cask: fixes for caveats output

Fixes #6470.

Maintainer's checklist on accepting formula PR

utils/curl.rb: accept 1xx HTTP status codes

Create '.keepme' files in directories

build: bump github-pages from 198 to 200 in /docs

Bumps [github-pages](https://github.com/github/pages-gem) from 198 to 200.
- [Release notes](https://github.com/github/pages-gem/releases)
- [Commits](https://github.com/github/pages-gem/compare/v198...v200

)

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

RFC 2616 states:

A client MUST be prepared to accept one or more 1xx status responses
prior to a regular response, even if the client does not expect a 100
(Continue) status message. Unexpected 1xx status responses MAY be
ignored by a user agent.

In the rare cases that we encounter a formula URL with a server that
provides a preliminary 1xx status code, it seems that (at least during
audit) we are failing on encountering this status code, even though
retrieving the file will succeed without issues.

In some cases, certain Casks shouldn't be resubmitted for specific reasons: difficult to maintain, developers maintain their own version, ...

To make sure these cases are restricted - we can add them to a blacklist and have the blacklist checked as part of the `brew cask audit` steps.

Fix `brew ruby -r`.

os/linux: add, use OS::Linux.os_version

Use AppleScript to check if GUI apps are running.

Docs: Add a link to the linuxbrew-core maintainer guide

- Also document some things that could go wrong and how to recover from
  them.