chore: Remove anthos-dpe from owners (#779)

* Remove anthos-dpe from owners

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

* Remove duplicate codeowner_team from metadata

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

java-container/.github/CODEOWNERS

@@ -4,9 +4,7 @@
 # For syntax help see:
 # https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners#codeowners-syntax
 
-# The @googleapis/anthos-dpe is the default owner for changes in this repo
-*                       @googleapis/yoshi-java @googleapis/anthos-dpe
-
+*                       @googleapis/yoshi-java
 
 # The java-samples-reviewers team is the default owner for samples changes
 samples/**/*.java       @googleapis/java-samples-reviewers

java-container/.repo-metadata.json

@@ -9,7 +9,6 @@
     "repo": "googleapis/java-container",
     "repo_short": "java-container",
     "distribution_name": "com.google.cloud:google-cloud-container",
-    "codeowner_team": "@googleapis/anthos-dpe",
     "api_id": "container.googleapis.com",
     "api_description": "is an enterprise-grade platform for containerized applications, including stateful and stateless, AI and ML, Linux and Windows, complex and simple web apps, API, and backend services. Leverage industry-first features like four-way auto-scaling and no-stress management. Optimize GPU and TPU provisioning, use integrated developer tools, and get multi-cluster support from SREs.",
     "transport": "grpc",