Fix bug in weaviate search method

[matanco1]

Description

Used score metadata for weaviate hybrid queries but always set score=1 as the code used distance instead of score
Fixed the issue by changing the if/else statement to use score

Also, changed the connection to weaviate cloud to the new interface introduced by the python package.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Refactor (does not change functionality, e.g. code style improvements, linting)

How Has This Been Tested?

All queries before returned score=1, now the score is settled.

Please delete options that are not relevant.

• Test Script (can't provide, but the fix is very simple, I don't think you need it)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

Maintainer Checklist

• closes #xxxx (Replace xxxx with the GitHub issue number)
• Made sure Checks passed

[parshvadaftari]

Looks good to me.

[parshvadaftari]

Thank you for your contributions @matanco1