[EUSM] Add sorting across all lists

[AnnieMungai]

When reviewing the different lists on web, user is not able to sort through the lists.

Required

• Add sorting across all the lists.
• Allow user to sort the list using different parameters.

Acceptance Criteria

• On all locations list, user can sort the locations by name and parent location- alphabetically or in reverse alphabetical order.
• On the all locations list - user can sort the list by the status - active or inactive (if we retain the inactive items on the list).
• On the inventory list - user can sort the service points by name and parent location- alphabetically or in reverse alphabetical order.
• On the all inventory list - user can sort the service point by the status - active or inactive (if we retain the inactive items on the list).
• On the product catalogue, user can sort the products by name alphabetically or in reverse alphabetical order.
• On the product catalogue, user can sort the products by whether attractive or not.
• On the product catalogue, user can sort the products by the status - active or inactive.

[peterMuriuki]

[ ] On all locations list, user can sort the locations by name and parent location- alphabetically or in reverse alphabetical order.

I do not know how we can sort locations by their parent name from the list view. The hapi fhir server does not expose an api that facilitates this out of the box, I could look at using custom search parameters but they have caused more problems than helped in the past.

Alternatively:

1. we can add a new filter by parent location on the location list view.

• On the product catalogue, user can sort the products by whether attractive or not.

I think this would be better handled as filters.

cc @AnnieMungai @dubdabasoduba

[peterMuriuki]

• On the product catalogue, user can sort the products by the status - active or inactive.

Also sort and filter is not by default available for Group.status.
Am afraid the precedent is that we might have to resort to fetching all the data and performing some of these actions client side. NOT IDEAL for scale