Update CODEOWNERS file

[andistorm]

Describe your changes

• add @andistorm to ci related files

• add @andistorm to cmake related files

• add @andistorm to ErrorHistory and error example modules

• add '/' to a couple of paths

Issue ticket number and link

Checklist before requesting a review

• I have performed a self-review of my code
• I have made corresponding changes to the documentation
• I read the contribution documentation and made sure that my changes meet its requirements

[AssemblyJohn]

The folders: https://github.com/EVerest/everest-core/tree/main/config
And the file: https://github.com/EVerest/everest-core/blob/main/dependencies.yaml

Are most of the time modified when integrating for example a new library version (libocpp, libevsesecurity, libiso), and at the moment any small change in those files require waiting on one of the generic code owners. Also a small requirement added to a module in a config, also waits on the generic code owners.

A bit more flexibility on those files that are modified quite often should be beneficial for faster merges.

[andistorm]

The folders: https://github.com/EVerest/everest-core/tree/main/config And the file: https://github.com/EVerest/everest-core/blob/main/dependencies.yaml

Are most of the time modified when integrating for example a new library version (libocpp, libevsesecurity, libiso), and at the moment any small change in those files require waiting on one of the generic code owners. Also a small requirement added to a module in a config, also waits on the generic code owners.

A bit more flexibility on those files that are modified quite often should be beneficial for faster merges.

Just had a quick look on who commited things there and added those people

[AssemblyJohn]

Looks a lot better for those frequently-modified files! Any thoughts @hikinggrass @corneliusclaussen @hikinggrass ?

[SebaLukas]

👍