Use the same pattern format for CODEOWNERS generation

What does this MR do and why?

• Use the same pattern format for CODEOWNERS generation
• Update CODEOWNERS for auth based on new files

I realized that CODEOWNERS actually will try to "normalize" the pattern before trying to match it, and we should follow the same format otherwise it'll be confusing what works and what not.

Follow up from !85937 (merged)

An important prerequisite for #362377 (closed)

Closes #363207 (closed)

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.