Sortable columns in module index, avoid [400] Unsupported sorting field

[didoda]

Sometimes in modules index page, the columns are considered sortable, even though they are not: a GET on BEdita APIs, with a sort by a non-sortable field, returns an error [400] Unsupported sorting field. This avoids that kind of error.

BEdita API don't provide in objects schema that information, whether a property can be used in ?sort=<prop> or not. So, the approach used is: some fields are considered always sortable (id, title, modified, date_ranges); all the other fields are considered not sortable, if they are not set in Properties.<objectType>.sortable configuration. An example follows:

{
  "bookings": {
    "sortable": ["booking_status"]
  }
}

Ref: https://github.com/bedita/manager/wiki/Setup:-Properties-display#sortable

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.64%. Comparing base (62e2b3c) to head (99abcae).
Report is 32 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #1213      +/-   ##
============================================
- Coverage     99.65%   99.64%   -0.01%     
+ Complexity     1326     1316      -10     
============================================
  Files            98       97       -1     
  Lines          5205     5122      -83     
============================================
- Hits           5187     5104      -83     
  Misses           18       18              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.