ci(github): potential CODEOWNERS syntax fix - one line per maintainer

[petermetz]

We've been having sytnax issues with the CODEOWNERS file for years where
GitHub is claiming that the usernames of certain maintainers don't exist
even though they defintely do.

This is an attempt to get that error unstuck by adding each wildcard
entry as its own line in the text file. Will be interesting to see if this
makes to false-positive syntax errors go away.

Signed-off-by: Peter Somogyvari peter.somogyvari@accenture.com

Pull Request Requirements

• Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

[jagpreetsinghsasan]

LGTM, but it is still showing errors @petermetz

[outSH]

I think the failing maintainers are not part of this org (https://github.com/orgs/hyperledger-cacti/people?query=) and not in maintainers team (https://github.com/orgs/hyperledger-cacti/teams/cacti-maintainers), that may be the main issue

[ryjones]

I think the failing maintainers are not part of this org (https://github.com/orgs/hyperledger-cacti/people?query=) and not in maintainers team (https://github.com/orgs/hyperledger-cacti/teams/cacti-maintainers), that may be the main issue

correct

[petermetz]

@ryjones @outSH @jagpreetsinghsasan Oh, OK, then this can be closed, thank you! :-)