BibIndex: do not use hstRECORD

* Disables the filtering step that uses `hstRECORD` table:
  set always `force_all_indexes=True` when calling
  `find_affected_records_for_index`

* Fixes `find_affected_records_for_index` when called with `recIDs=[]`

* Fixes a regression test

Signed-off-by: Federico Poli <federico.poli@cern.ch>
I think that disabling the `hstRECORD` lookup bibindex indexes more records, so there are more tokens in the queue and the `(19, 19, 'keyword')` row is no more the first one.
Maybe is better to check that the number of occurences of `(19, 19, 'keyword')` increased?