Describe the bug

Browse page results aren't sorted as configured in REST

• The configured sort direction is not taken into account

• The sort type / order cannot be set for metadata indices, even though this should be possible [according to the documentation](https://wiki.lyrasis.org/display/DSDOC7x/Configuration+Reference#ConfigurationReference-DefiningtheIndexes)

  If you set a <sort-type> to be used, this sort type is not used on the values of the metadata fields but on the order of the items when listing all items that have a specific value of the metadata field.

• The default configuration sorts dates in ascending order, even though the documentation mentions that

  descending may be useful for date-based indexes

To Reproduce

Steps to reproduce the behavior:

1. Run a local DSpace instance with the following browse configuration

   webui.browse.index.1 = dateissued:item:dateissued:desc
   webui.browse.index.2 = author:metadata:dc.contributor.*\,dc.creator:text:desc:dateissued
   

2. Open the "by issue date" browse page
   • Angular will send a request with sort=default,ASC
   • The response will be sorted by ascending date
3. Re-send that request without the sort parameter
   • The response will be sorted by descending date, as configured
4. Open the "by author" browse page
   • Angular will send a request with sort=default,ASC
   • The REST request will fail with HTTP 500, the following error will appear in the log

     2023-01-31 13:01:43,944 ERROR 2472f5f8-fc56-476e-9868-25549c647e08 755495a6-7d3f-43a8-9237-e3f25a13bb2b org.dspace.app.rest.exception.DSpaceApiExceptionControllerAdvice @ An exception has occurred (status:500)
     java.lang.IllegalStateException: The requested browse doesn't provide direct access to items you must specify a filter
     	at org.dspace.app.rest.repository.BrowseItemLinkRepository.listBrowseItems(BrowseItemLinkRepository.java:82) ~[classes/:?]
       ...
     

Expected behavior

• When no sort direction is specified, browse pages should sort results as configured in REST.
• When no sort direction is specified, Angular should update the "pagination component" to reflect the default sort direction as configured in REST.

General thoughts

While working on #8642 @YanaDePauw noted that browse could be replaced with discovery/Solr facets.
IMO this may be a more worthwhile time investment than maintaining it.