issue #46: update search sources

[k-allagbe]

Closes #46
Closes #13

• update debug panel
• integrate azure search
• handle azure hit highlighting
• fix backend ping
• fix debug panel position when there is no warning
• manual tests
• automated tests
• update version
• documentation
• manual test documentation

[rngadam]

don't forget to provide before and after screenshots

[k-allagbe]

don't forget to provide before and after screenshots

Before:

After:

[rngadam]

add tasks for documentation, automated testing, versioning (_versions.ts) and documenting the manual tests as per:

ai-cfia/nachet-frontend#72

[CFIALeronB]

@k-allagbe New Debug Panel looks good! Only issue I found durring testing is that static results were not populated once the user selects a static response option:

[k-allagbe]

@k-allagbe New Debug Panel looks good! Only issue I found durring testing is that static results were not populated once the user selects a static response option:

This is probably because your instance was not pointing on a finesse-backend. Make sure finesse-backend is running and the env var is pointing to it.

[vivalareda]

Sorry for amount of deployment messages but I had test a lot to figure out a fix. I changed the reusable workflow to install the npm version used in the lint-test and required from the package.json's engines

[k-allagbe]

Sorry for amount of deployment messages but I had test a lot to figure out a fix. I changed the reusable workflow to install the npm version used in the lint-test and required from the package.json's engines

I would suggest adding the ability to pass the versions as parameter if possible in all related reusable workflows to avoid any future discrepancy. @rngadam ?

[vivalareda]

Sorry for amount of deployment messages but I had test a lot to figure out a fix. I changed the reusable workflow to install the npm version used in the lint-test and required from the package.json's engines

I would suggest adding the ability to pass the versions as parameter if possible in all related reusable workflows to avoid any future discrepancy.

Sorry for amount of deployment messages but I had test a lot to figure out a fix. I changed the reusable workflow to install the npm version used in the lint-test and required from the package.json's engines

I would suggest adding the ability to pass the versions as parameter if possible in all related reusable workflows to avoid any future discrepancy.

Should be checked with Ricky since version is hardcoded in lint-test maybe it's for consistency across the repositories but it can be added forsure