Question about using Homebrew in Azure CI. Did we set this up or is the Homebrew install managed by Azure? I'm noticing inconsistencies between using brew locally and with Azure. (1) adoptopenjdk8 is no longer a valid cask after some refactoring upstream, but it still works in Azure. (2) We need the Homebrew fix referenced here https://github.com/osquery/osquery/pull/5845/files#diff-fec826feae04e51c0d94076385408bdcR210 and this has been merged upstream (recently) and works locally, but not in Azure. Based on these experiences it looks like the Azure Homebrew is pinned somehow?