Ensure that all non-vendored source files use the ASF specific license header

### Affected version

1.0.4

### Bug description

This release contains files which use the generic Apache License 2.0 header instead of the [source file header for ASF code](https://www.apache.org/legal/src-headers.html#headers) mandated by the ASF release policy. The cause is that this code was donated and [IP cleared in 2021](https://incubator.apache.org/ip-clearance/maven-daemon.html), and the donated code contained the generic header. The IP clearance documentation says to "[c]heck and make sure that the files that have been donated have been updated to reflect the new ASF copyright", but apparently some files were accidentally skipped. An example is `build/publish-on-homebrew.sh`.

The background is that ASF Tooling received a report from @cstamas that [some files were failing license header checks in ATR](https://the-asf.slack.com/archives/C049WADAAQG/p1773411579684159?thread_ts=1773404398.452299&cid=C049WADAAQG). We investigated and came to the conclusions above. We were [asked](https://the-asf.slack.com/archives/C049WADAAQG/p1773845040375749?thread_ts=1773404398.452299&cid=C049WADAAQG) to file this bug report with our findings, and the linked thread contains further detail.

Start by auditing non-vendored source files, beginning with build/publish-on-homebrew.sh and the ASF source-header guidance linked in the issue. Done means every applicable source file uses the ASF-specific header while vendored files remain excluded; the issue does not name a test to run.

Written by the indexing model from the issue text.