Feature: sort-intersection-types and anonymous types

[Evalon]

What rule do you want to change?

sort-intersection-types

Describe the problem

Consider this type: { apiKey: string | null } & Config I think it's better for readability if named (aliased) types (Config) are followed by anonymous types ({ apiKey: string | null }). Also, it feels more explicit in intention.

Code example

constructor(props: { apiKey: string | null } & Config) {
    super(props)
    this.apiKey = props.apiKey
}
--- VS
constructor(props: Config & { apiKey: string | null }) {
    super(props)
    this.apiKey = props.apiKey
}

Additional comments

No response

Validations

• [X] Read the docs.
• [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.