consistent-type-specifier-style: rename prefer-top-level

[privatenumber]

Problem

Currently, the consistent-type-specifier-style rule has options prefer-top-level and prefer-inline.

While it uses the word "prefer", it doesn't seem to be preferential—but more of a requirement—as prefer-top-level errors on:

import { valueA, type typeB } from './file'

Proposal

1. Rename the current options to top-level and inline

2. Add a new prefer-top-level that only errors if it's possible to move the type to the top-level without causing a duplicate import:

   // Passes
   import { valueA, type typeB } from './file' // can be inline because making it top-level will require a separate import for valueA
   
   // Errors
   import { type typeB } from './file' // type should be top-level

[SukkaW]

We can add top-level and inline as aliases for now. Changing the prefer-top-level would be a breaking change.