dbDelta index ASC or DESC creates duplicate

[mnelson4]

Similar to #10404,
using
KEY movie_type_idx (movie_type ASC), creates duplicate indexes, whereas using
KEY movie_type_idx (movie_type), does not.
Although specifying the order of the index apparently doesn't affect anything according to ​http://dev.mysql.com/doc/refman/5.7/en/create-index.html. Specifically it states

An index_col_name specification can end with ASC or DESC. These keywords are permitted for future extensions for specifying ascending or descending index value storage. Currently, they are parsed but ignored; index values are always stored in ascending order.

[ocean90]

In 37583:

Database: Normalize index definitions in dbDelta().

dbDelta() compares the index definitions against the result of SHOW INDEX FROM $table_name. This requires a specific format so indices are not unnecessarily re-created. This format wasn't ensured, until now.

• Parse the raw index definition to extract the type, name and columns so a normalized definition can be built (#20263, #34873).
• Standardize on uppercase types (#34871) and on 'KEY'. 'INDEX' is only a synonym for 'KEY'.
• Escape index names with backticks (#20263).
• Normalize columns: Ignore ASC and DESC definitions (#34959), remove whitespaces (#34869) and escape column names with backticks (#20263).
• Add backticks to all index change queries (#20263).

Props ocean90, pento, kurtpayne.
Fixes #20263, #34869, #34871, #34873, #34959.