refactor!: improve the deserialization logic for components that use a Document Store

[anakin87]

Related Issues

• fixes Pipeline deserialization fails if the Document Store has not been previously imported #6473

Proposed Changes:

• Improve the deserialization logic for components that use a Document Store.
  It will no longer be necessary to first import the Document Store used to deserialize Pipelines without errors.

• Remove the @document_store decorator and the registry of Document Stores.

How did you test it?

CI, adapted the tests.

Notes for the reviewer

After this change, we should remove the decorator from the Document Stores in haystack-core-integrations.

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[silvanocerza]

Can we maybe remove the decorator in a later PR?
Otherwise we're going to break all the Document Stores already published, would be great if first we take care of removing the decorator from those and then actually remove it.

[anakin87]

Can we maybe remove the decorator in a later PR? Otherwise we're going to break all the Document Stores already published, would be great if first we take care of removing the decorator from those and then actually remove it.

I removed the decorator from the Document Stores in deepset-ai/haystack-core-integrations#76
I also published new releases for Elasticsearch, Opensearch and Chroma Document Stores.

[masci]

Good to go, I would probably isolate the module-loading logic in an utility method at some point but let's merge