Sniff to enforce naming conventions for class/function/const aliases

[jrfnl]

Is your feature request related to a problem?

It would be nice to have a sniff which could check that an alias name provided in import use statements and trait use statements complies with certain naming conventions.

The most common naming convention for class names would probably be StudlyCaps/PascalCase.
Along the same lines, the most common naming convention for function names would probably be camelCase, while for constants it would be MACRO_CASE.

Supporting other naming conventions for each should also be considered.

Describe the solution you'd like

A new sniff with a choice of which naming convention to enforce for each type of alias.

Some examples:

// StudlyCaps/PascalCase class aliases.
use Vendor\Package\ClassName as MyClass; // OK.
use Vendor\Package\ClassName as myClass; // Not OK.
use Vendor\Package\ClassName as My_Class; // Not OK.

// camelCase function aliases.
use function Vendor\Package\functionName as myFunction; // OK.
use function Vendor\Package\functionName as my_function; // Not OK.

class Aliased_Talker {
    use A, B {
        B::bigTalk as talk; // OK
        B::smallTalk as TALKING; // Not OK.
    }
}

// MACRO_CASE constant aliases,
use const Vendor\Package\CONSTANT_NAME as MY_CONSTANT; // OK.
use const Vendor\Package\CONSTANT_NAME as myCONSTANT; // Not OK.

Additional context (optional)

Might be a good idea for the sniff to also check that aliases also complies with the following additional conventions:

• No leading underscore(s).
• No trailing underscore(s).