[DURACOM-506] added spellcheck support

[steph-ieffam]

References

• Fixes "Did you mean" Spellcheck feature doesn't exist on search page #1480

Relates to

DSpace/RestContract#359
DSpace/DSpace#12792

Description

Added support for Spellcheck "did you mean?" feature whose porting from version 6 was not completed

Instructions for reviewers

• Create items with dc.title set to test
• Run the following script ./dspace index-discovery --spellchecker to rebuild the spellchecker index
• Type in the search box testi
• You'll get displayed the correct suggested query in the search page
  Alternatively this test could be run using any other item in the repository trying to use a misspelled query.
  The result strictly depends on the on the content indexed on Solr as already defined in the Solr configuration

Checklist

• My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• My PR passes ESLint validation using npm run lint
• My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
• My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
• My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
• My PR aligns with Accessibility guidelines if it makes changes to the user interface.
• My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
• My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
• If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
• If my PR fixes an issue ticket, I've linked them together.