searchApi: fix response interceptors and suggestion config validation

[bodoque-01]

❤️ Thank you for your contribution!

Description

This PR fixes some bugs in the search API layer.

Response Interceptors

InvenioSearchApi and OSSearchApi registered config.interceptors.response on axios.interceptors.request instead of .response, so response interceptors never ran. Now, both APIs use interceptors. response.use, with tests asserting that the handler receives {status, data}.

InvenioSuggestionApi config

validateConfig was orphaned after the parent renamed validateConfig to validateAxiosConfig (commit in 2020) and was never called from the constructor path.

Query state

updateQueryStateAfterResponse deleted response.newStateQuery instead of response.newQueryState

Impact

Bundled demos (e.g. OpenSearch on localhost:5000) behave the same on the default path, I think the fixes matters only (correct me if wrong!) when anyone who uses it uses response interceptors.
Besides adding tests, I too tested manually by adding some silly mock interceptor and verified via console logs that it indeed was being included in the logic when searching.

Checklist

Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

• I'm aware of the code of conduct.
• I've created logical separate commits and followed the commit message format.
• I've added relevant test cases.
• I've added relevant documentation. (No doc changes)
• I've marked translation strings. (No translation changes)
• I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
• I've NOT included third-party code (copy/pasted source code or new dependencies).
  • If you have added third-party code (copy/pasted or new dependencies), please reach out to an architect on Discord.

Frontend

• I've followed the CSS/JS and React guidelines. (No frontend changes)
• I've followed the web accessibility guidelines. (No frontend changes)
• I've followed the user interface guidelines. (No frontend changes)

Reminder

By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

1. You license your contribution under the same terms as the current repository’s license.
2. You agree that you have the right to license your contribution under the current repository’s license.