ci(component-owners): try using component-owners

Try using component-owners intead of CODEOWNERS since the latter
requires write permission to the repo.

Signed-off-by: Randolph Sapp <[email protected]>

.github/component-owners.yml

@@ -0,0 +1,32 @@
+---
+# Each component identified by its path prefix has a list of owners
+components:
+
+  # Ownership applies recursively to any file in a directory
+
+  ./:
+    - cshilwant
+    - StaticRocket
+    - praneethbajjuri
+    - uditkumarti
+
+  source/buildroot/:
+    - TexasInstruments/sitara-mpu-linux-sdk
+
+  source/debian/:
+    - TexasInstruments/sitara-mpu-linux-sdk
+
+  source/system/:
+    - TexasInstruments/sitara-mpu-linux-sdk
+
+  source/linux/Overview/:
+    - TexasInstruments/sitara-mpu-linux-sdk
+
+  source/linux/Foundational_Components/:
+    - praneethbajjuri
+    - uditkumarti
+    - r-vignesh
+
+  source/linux/Foundational_Components/Power_Management/:
+    - praneethbajjuri
+    - DhruvaG2000

.github/workflows/component-owners.yml

@@ -0,0 +1,31 @@
+---
+name: "component-owners"
+
+on:
+  # It's insecure to use pull_request_target if you intend to check out code
+  # from that PR. This just reads the config file in the pull request base, and
+  # is not an issue currently. We will need to use this to comment on PRs coming
+  # from forked repositories.
+  pull_request_target:
+    branches: [master]
+
+permissions:
+  # Clamp permissions since pull_request_target workflows granted full
+  # read/write repository permission by default
+  contents: read
+  issues: write
+  pull-requests: write
+
+jobs:
+  component-owners:
+    name: Assign component owners
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Assign component owners
+        uses: dyladan/component-owners@main
+        with:
+          config-file: .github/component-owners.yml
+          repo-token: ${{ github.token }}
+          assign-owners: true
+          request-owner-reviews: true