Rule Request: Prefer CGRect over NSRect

New Issue Checklist

• Updated SwiftLint to the latest version
• I searched for existing GitHub issues

Rule Request

1. Why should this rule be added? Share links to existing discussion about what
   the community thinks about this.

CGRect and NSRect are the same. NSRect is just a typealias of CGRect. I would like to enforce CGRect for consistency with iOS code.

This would apply to:

• NSRect => CGRect
• NSSize => CGSize
• NSPoint => CGPoint

2. Provide several examples of what would and wouldn't trigger violations.

Would trigger:

NSSize(width: 100, height: 100)

let foo: NSSize = bar()

Would not trigger:

CGSize(width: 100, height: 100)

let foo: CGSize = bar()

3. Should the rule be configurable, if so what parameters should be configurable?

No, there's nothing to configure.

4. Should the rule be opt-in or enabled by default? Why?
   See README.md for guidelines on when to mark a
   rule as opt-in.

I think it should be enabled by default as there's really no good reason to use the NS versions. They're just type aliases to the CG versions and most people use them inconsistently anyway.

Start with the opt-in rule guidance in README.md and the requested examples in this issue. The change is complete when NSRect, NSSize, and NSPoint usages are reported as their CGRect, CGSize, and CGPoint counterparts, while the CG forms do not trigger violations.