"Ordinal" versus "Priority" is confusing

Describe the bug

For ConfigSource we talk about “ordinal”, which is a word that means “relating to position in a series”, for example (first, second, third, etc.). For other things we use “priority” (and the @Priority annotation). This is very confusing because when we talk about ordinals in language, the thing that is first is first, but we’re now treating ConfigSource ordinality the reverse way: higher (or later) ordinals take effect over lower (or earlier) ordinals.

We should change all specification language referring to “ordinal” to say “priority” instead. We should also look into using @Priority for ConfigSource by default (possibly as a follow-up issue).

[radcortez]

The pain point here will be the ConfigSource#getOrdinal method.

[Emily-Jiang]

The above statement is only about invocation order not about which wins. In CDI spec: https://jakarta.ee/specifications/cdi/3.0/jakarta-cdi-spec-3.0.html#unsatisfied_and_ambig_dependencies

All the beans left are alternatives with a priority, or producer methods or fields of beans that are alternatives with a priority, then the container will determine the highest priority value, and eliminate all beans, except for alternatives with the highest priority and producer methods and fields of alternatives with the highest priority value. If there is exactly one bean remaining, the container will select this bean, and the ambiguous dependency is called resolvable.

It clearly specifies the highest priority wins, which is the behaviour we are having here as well.