Code owners: Remove users without write access and fix typos

[ocean90]

Description

The current CODEOWNERS files contains a few errors which you should see when open the file on GitHub.

List of errors

Unknown owner on line 11: make sure @coderkevin exists and has write access to the repository
…                      @nerrad @coderkevin
Unknown owner on line 86: make sure @jaymanpandya exists and has write access to the repository
…                   @ajitbohra @jaymanpandya
Unknown owner on line 87: make sure @jaymanpandya exists and has write access to the repository
…                   @ajitbohra @jaymanpandya
Unknown owner on line 88: make sure @jaymanpandya exists and has write access to the repository
…                   @ajitbohra @jaymanpandya
Unknown owner on line 89: make sure @jaymanpandya exists and has write access to the repository
…                   @ajitbohra @jaymanpandya
Unknown owner on line 90: make sure @jaymanpandya exists and has write access to the repository
…                   @ajitbohra @jaymanpandya
Unknown owner on line 91: make sure @jaymanpandya exists and has write access to the repository
…                   @ajitbohra @jaymanpandya
Unknown owner on line 133: make sure @timothybjabocs exists and has write access to the repository
…                              @timothybjabocs @spacedmonkey @oandregal
Unknown owner on line 135: make sure @timothybjabocs exists and has write access to the repository
…                              @timothybjabocs @spacedmonkey @oandregal
Unknown owner on line 136: make sure @timothybjabocs exists and has write access to the repository
…                              @timothybjabocs @spacedmonkey @oandregal
Unknown owner on line 137: make sure @timothybjabocs exists and has write access to the repository
…e-json-gutenberg.php          @timothybjabocs @spacedmonkey @oandregal
Unknown owner on line 138: make sure @timothybjabocs exists and has write access to the repository
…e-json-resolver-gutenberg.php @timothybjabocs @spacedmonkey @oandregal
Unknown owner on line 139: make sure @janw-me exists and has write access to the repository
…                              @janw-me
Unknown owner on line 151: make sure @ghost exists and has write access to the repository
…                              @ghost
Unknown owner on line 152: make sure @ghost exists and has write access to the repository
…                              @ghost
Unknown owner on line 153: make sure @ghost exists and has write access to the repository
…                              @ghost
Unknown owner on line 154: make sure @ghost exists and has write access to the repository
…                              @ghost
Unknown owner on line 155: make sure @ghost exists and has write access to the repository
…                              @ghost
Unknown owner on line 156: make sure @ghost exists and has write access to the repository
…                              @ghost

This PR removes users which seem to no longer have write access and fixes a typo in timothybjacobs. The remaining errors are for the native files which should be unowned. Based on the example (last line) I'm wondering if keeping it empty would be enough too? It seems like that wasn't clear when introduced in #13675.

[gziolo]

The remaining errors are for the native files which should be unowned. Based on the example (last line) I'm wondering if keeping it empty would be enough too? It seems like that wasn't clear when introduced in #13675.

Yes, it is very likely that you can just simply leave it empty to avoid having everyone being notified. In the past, it worked differently so we used a random GitHub's bot account that was mentioned on Stackoverflow 😄

[gziolo]

Let's see what happens 😅