zerocopy: add SPDX-License-Identifier to source files

[Sagartaunk]

Fixes #3428

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.85%. Comparing base (8d7db04) to head (97b5894).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3432   +/-   ##
=======================================
  Coverage   91.85%   91.85%           
=======================================
  Files          20       20           
  Lines        6093     6093           
=======================================
  Hits         5597     5597           
  Misses        496      496           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[joshlf]

Tiny nit, but otherwise looks good, thanks! You'll also need to rebase on main.

[joshlf]

Oh and also, you'll need to run ./tools/update-expected-test-output.sh after you've made any changes.

[Sagartaunk]

Oh and also, you'll need to run ./tools/update-expected-test-output.sh after you've made any changes.

Made the changes and rebased on main. Also, are there any good first issues you'd recommend to someone looking to contribute more?

[Sagartaunk]

I have removed the accidental generated-output churn, and the branch now contains only the SPDX changes in .rs files. I haven’t committed the UI expected-output changes because running ./tools/update-expected-test-output.sh also modifies the bench output on my machine, I am not sure why. Since those bench changes seem unrelated to this PR, I left all generated output out for now.

[joshlf]

Looks like I can't push to your branch, but I put up a new PR with your commit (but rebased and having re-run the UI test generation): #3455.

[Sagartaunk]

Looks like I can't push to your branch, but I put up a new PR with your commit (but rebased and having re-run the UI test generation): #3455.

Thanks, should i close this one ?

[joshlf]

Yeah I was waiting to see whether the tests passed on the other one, which they now have, so closing this.