Disable filtering and sorting on columns that do not have an index

Columns that do not have an index defined should be removed from the dropdown lists for filtering and sorting. This will avoid users putting too much load on the database. See below for further details.

All columns can still be selected for viewing data in them.

The changes requested in https://folio-org.atlassian.net/browse/MODLDP-30 can be used to generate an "index_types" column in mod-ldp that indicates which columns have indexes.

Logic:

• If a column has a "btree" index, it can be used for filtering using the =, <>, <, <=, >, and >= operators, as well as for sorting. At this time (PostgreSQL 14), only a "btree" index can be used for sorting.

• If a column has a "gin" index, it can be used for filtering using the LIKE and ILIKE operators.

• Otherwise filtering and sorting should be disabled for the column.

(Adding support for the LIKE and ILIKE operators is not necessarily within the scope of this issue, though at this level of implementation their usage is basically interchangeable with the other operators listed above.)