fix(akita): restrict usage of sortByOrder to valid usages in type system

[cgrabmann]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/datorama/akita/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

When using getAll or selectAll from a QueryEntity and providing a sortBy function, the sortByOrder is ignored. This is not represented in the type system and therefore lead to some initial confusion in our team.

Issue Number: N/A

What is the new behavior?

sortByOrder can no longer be provided when providing a sortBy function. This is now restricted by the type system.

sortByOrder can can still be provided when providing a sortBy field.

Does this PR introduce a breaking change?

• Yes
• No

Projects that provided a sortByOrder and a sortBy function will have a failing build and need to remove the sortByOrder

Other information

[NetanelBasal]

Thanks, we'll merge it in v7