remove a new test from TCK

[gavinking]

This test, which was added yesterday, requires dynamically sorting by fields which are not selected. As far as I know, the specification does not explicitly require this, and in traditional SQL, sorting by unselected fields is something that is not usually considered allowed, though it's true that many databases are quite forgiving here.

Now, it's true that I didn't disallow this in JDQL, but there's a big difference between allowing it statically and allowing it for dynamically-added sorting.

Actually I probably should have disallowed it in JDQL, because in fact JPQL disallows it in section 4.10 of the latest Persistence spec. (Again, actually-existing JPQL implementations do allow it.) I will follow up with a PR that adds a caveat about this to section 5.5.5.

Folks, I think at this late stage we should try hard to avoid adding "weird" new corner-casey things like this to the TCK. Let's stick to bread-and-butter things which we know are supposed to work and leave stuff like this alone for now.

[gavinking]

See #627.

[njr-11]

This isn't a new test that I added to the TCK for the purpose of testing unusual usage. It's from my attempt to correct an error in the TCK where it was requiring a type parameter on the repository super interface. The method that I was fixing already performed a find operation and had dynamic sorting for it, with these same asserted outputs. Unfortunately, the fix I made to restrict the return type to only the id in order to avoid the type parameter turned out to be in conflict with the dynamic sorting by other entity attributes. Instead of removing the test, we should correct it, otherwise we lose coverage. I added suggestions to switch the dynamic ordering to static.

[gavinking]

Ah, OK, apologies, I thought it was new.

Applied your suggestions.