chore: regenerate common config

[yoshi-automation]

This PR was generated using Autosynth. 🌈

Synth log will be available here:
https://source.cloud.google.com/results/invocations/a89ada08-4dfb-47d5-b8f7-042aafb7f10f/targets

• To automatically regenerate this PR, check this box.

[codecov]

Codecov Report

Merging #186 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master    #186   +/-   ##
========================================
  Coverage      0.41%   0.41%           
  Complexity       19      19           
========================================
  Files            12      12           
  Lines         13375   13375           
  Branches       2620    2620           
========================================
  Hits             55      55           
  Misses        13317   13317           
  Partials          3       3           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5b7694d...6214834. Read the comment docs.

[BenWhitehead]

@JustinBeckwith synth doesn't seem to know that this repo should have yoshi-java as a code-owner and is trying to undo the part of the change from #181. Do you know why this might be happening?

[stephaniewang526]

@JustinBeckwith synth doesn't seem to know that this repo should have yoshi-java as a code-owner and is trying to undo the part of the change from #181. Do you know why this might be happening?

Hi @BenWhitehead -- i think you need to set codeowner_team property in .repo-metadata.json in order for the correct CODEOWNERS team to be generated by synthtool. Example of setting the metadata in bigquerystorage repo and the generated template change.

.github/sync-repo-settings.yaml is used to grant teams correct permissions to the repo so that CODEOWNERS can be actually effective (for instance, if we added @googleapis/yoshi-java as CODEOWNER in this repo but did not grant it Write permission, it won't be assigned when a PR is proposed).

With this said, I think all you need to do here is to add codeowner_team property in .repo-metadata.json in this repo.

Hope this helps! cc @chingor13

[BenWhitehead]

Fixed config file in #192 which incorrectly resulted in the proposed change