Add oxlint as a peer dependency with a tight version constraint so users are less likely to have the two packages de-synced

[connorshea]

Right now, there's nothing to really stop the user from using oxlint 1.25.0 and eslint-plugin-oxlint 1.38.0, or vice-versa. It may be a good idea to add a peerDependency to the package.json to at least softly enforce that the versions match.