Rule Request: Protocol conformance order

New Issue Checklist

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

New rule request

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

Similar to the modified_order rule, it would be useful to be able to enforce the order of built-in protocols in a conformance. And also enforce that built-in protocols come first.

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

Would trigger:

struct Foo: RawRepresentable, Hashable {}

struct Foo: CustomProtocol, Hashable {}

Would not trigger:

struct Foo: Hashable, RawRepresentable {}

struct Foo: Hashable, CustomProtocol {}

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

No

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.

Enabled by default

Start by comparing the requested behavior with the linked modified_order rule and its documentation in Rules.md. Read README.md's opt-in-rule guidance, then define the built-in protocol ordering and verify the supplied triggering and non-triggering examples. Done means the new rule enforces that ordering and places built-in protocols before custom protocols.