Create "Configuration class ordering" rule(s)

According to the [migration guide](https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-4.x#configuration-class-ordering):

> Spring Framework 4.2 comes with significant fine-tuning in configuration class processing. There may be subtle differences in the order of registration compared to 4.1; however, those are considered fixes of behaviour that wasn't well-defined previously. If you are relying on a specific order, e.g. for overriding beans by name, please consider using 4.2's new facilities, in particular @Order annotations on config classes.

Investigate and create rules if necessary for this new behaviour.

In the rule description and message, try to be as verbose and clear as possible. Code examples are always welcome and useful. Feel free to use markdown syntax for these.

Start with the linked Spring Framework 4.x migration guide, especially its section on configuration class ordering and @Order annotations. Determine which ordering behaviors are detectable and whether rules are warranted; done means any justified rules include clear, verbose descriptions, messages, and useful Markdown examples, or a documented conclusion that no rule is needed.

Written by the indexing model from the issue text.