Add codeowners for Calyx

[rachitnigam]

Fixes #5543.

Attempt to allocate the owners based on previous file commit histories for now. My suggestion is that we keep it pretty liberal going forward so that people can take ownership of various passes as they evolve.

[andrewb1999]

LGTM! Happy to be a Calyx code owner.

[darthscsi]

Thanks all

[mikeurbach]

Works for me.

I'll add myself for CalyxToHW, since I added at least the initial version of that pass. I will also be happy to be added on LoopScheduleToCalyx, since I worked on the parts that are different from SCFToCalyx. I can add myself in a future commit, or if this PR is updated, feel free to add me.

@mortbopet - would you be willing to be added as a codeowner for SCFToCalyx with me? I have some familiarity, but sometimes I need to ask your opinion anyway.

[rachitnigam]

@mikeurbach (and everyone else) Please feel free to add yourself to relevant things. I didn't have all of the interest overlaps in my mind so definitely missed some things

[rachitnigam]

(Added @mikeurbach to HW and LoopSchedule)

[mortbopet]

@mikeurbach Yea, sign me up for SCFToCalyx.
@rachitnigam please remove me as a codeowner for Calyx - it's not that i don't want to be part of Calyx discussions and PRs, it moreso that I'm trying to spread out the burden of codeownership in CIRCT, and not have my name on too many different things and dialects (which will increase in the near future...).

[rachitnigam]

@mortbopet done with the changes. Looks like we have consensus on the ownership! Let's merge if there are no more changed needed

[dtzSiFive]

This looks ready to merge, would you like to do the honors @rachitnigam ?