adding codeowners

[sean-sype-simmons]

Description

Related Issue

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

• I have read the CONTRIBUTING document.
• I have run the pre-merge tests locally and they pass.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
• All new and existing tests passed.
• All commits have been signed-off for the Developer Certificate of Origin.

[Copilot]

Pull request overview

This PR adds a GitHub CODEOWNERS file to establish code review ownership for the repository. The change designates @brianLoomis and @sean-sype-simmons as default code owners for all files in the repository.

Key Changes

• Creates a new CODEOWNERS file with a wildcard pattern assigning repository-wide ownership to two users

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

[nitpick] The CODEOWNERS pattern uses excessive whitespace between the wildcard and the owners. Consider using a single space for consistency: * @brianLoomis @sean-sype-simmons

Suggested change

	* @brianLoomis @sean-sype-simmons
	* @brianLoomis @sean-sype-simmons