feat: add pytest-vcr for recording HTTP interactions in integration tests

[sergerdn]

Using pytest-vcr in integration tests has several benefits. Firstly, it removes the need to mock external services, as VCR records and replays HTTP interactions on the fly. Secondly, it simplifies the integration test setup by eliminating the need to set up and tear down external services in some cases. Finally, it allows for more reliable and deterministic integration tests by ensuring that HTTP interactions are always replayed with the same response.
Overall, pytest-vcr is a valuable tool for simplifying integration test setup and improving their reliability

This commit adds the pytest-vcr package as a dependency for integration tests in the pyproject.toml file. It also introduces two new fixtures in tests/integration_tests/conftest.py files for managing cassette directories and VCR configurations.

In addition, the tests/integration_tests/vectorstores/test_elasticsearch.py file has been updated to use the @pytest.mark.vcr decorator for recording and replaying HTTP interactions.

Finally, this commit removes the documents fixture from the test_elasticsearch.py file and replaces it with a new fixture defined in tests/integration_tests/vectorstores/conftest.py that yields a list of documents to use in any other tests.

This also includes my second attempt to fix issue : #2386

Maybe related #2484

[sergerdn]

@hwchase17

I'm ready for review now.

[hwchase17]

one comment around dependencies - otherwise love it - thanks

[sergerdn]

I am finished. Perhaps I made some mistakes, which I will correct in the next PR if necessary. I have some plans to improve the tests Elastic.

[hwchase17]

I am finished. Perhaps I made some mistakes, which I will correct in the next PR if necessary. I have some plans to improve the tests Elastic.

thanks, that would be great - im excited to try elastic more, so would love any more tests

also, are you on twitter or anything?? i love all your contributions, want to give you a shout out :)

[sergerdn]

I am finished. Perhaps I made some mistakes, which I will correct in the next PR if necessary. I have some plans to improve the tests Elastic.

thanks, that would be great - im excited to try elastic more, so would love any more tests

also, are you on twitter or anything?? i love all your contributions, want to give you a shout out :)

Thanks for your message! I just want to clarify that I'm not a professional programmer, but I do have some technical skills. I'm glad to hear that you're excited to try out Elastic more and conduct more tests. I should mention that I'm not a big specialist with Elastic myself, but I'm happy to help in any way I can. Unfortunately, I'm not on Twitter or any other social media platforms.

However, I have a friend who is more experienced with Elastic and may be able to provide more specialised support and guidance.

P.S.
If you would like to contact me personally, please leave a comment below with your email address. I will receive an email notification from GitHub. If you would like to keep your email private, you can delete it a few minutes after sending your message.

[sergerdn]

If possible, please merge those changes as soon as possible because I need to continue working. Thank you very much for your understanding.