[UX] Views: Hide the "sort by" option in the views creation wizard if there is no option to sort by

[klonos]

Steps To Reproduce

1. Start creating a views by navigating to admin/structure/views/add
2. Notice how the default "Show" option is "Content", and how that has various options for "of type", "tagged with", and "sorted by"
3. Start selecting all the the various available options in the "Show" select, and notice how the "of type", "tagged with", and "sorted by" form elements are being shown/hidden via #states, depending on what is relevant to each option 👍🏼
4. Notice how when you select "Taxonomy terms", the "sorted by" select has only a single "unsorted" option when you click on it 👎🏼
5. Notice how the same thing happens for the "Module/Theme/Theme engine" and "URL redirects" options 👎🏼

Actual behavior

As an end user, when clicking these "sorted by" selects only to find that the already selected option is the only option, I feel like the software is telling me "Ha! I made you look 😛" and it wastes my time by making me click on things that provide no value and have absolutely no reason to be there in the first place.

Expected behavior

If there is no available option to sort by, hide the select element via #states. UX++

[indigoxela]

@klonos I belief, that's a "works as designed" - it depends on the 'click sortable' => FALSE, definition, which is there for a reason.

Sorting would happen on database query level, but for some fields (that aren't, for example, actual db table columns) that's simply impossible.

If I misunderstood, please add some examples and possibly screenshots.