ci: update code owners

[joshua-white]

Update codeowners list to ensure at least three owners for each file. Trying to balance having strict ownership vs no-ownership. Can make changes later if we run into poor review issues.

Also updating ACKNOWLEDGEMENTS and CODE_OF_CONDUCT to fix email and cited organizations.

[dkachuma]

I feel that the current code owners file may be a bit too granular, especially given that we don't have a large number of active reviewers to support that level of detail. The fine-grained structure makes ownership harder to manage and slows down the review process.

Perhaps we could consider consolidating some of the code areas into broader categories. This might help simplify the file, make ownership clearer, and better align with the available reviewer capacity.

[rrsettgast]

I feel that the current code owners file may be a bit too granular, especially given that we don't have a large number of active reviewers to support that level of detail. The fine-grained structure makes ownership harder to manage and slows down the review process.

Perhaps we could consider consolidating some of the code areas into broader categories. This might help simplify the file, make ownership clearer, and better align with the available reviewer capacity.

codeowners is inherently at directory level granularity. Lower levels override upper levels. So the only things that have extra granularity more than the component level is inputFiles, constitutive, and physicsSolvers. This makes some sense to have this level of granularity.