test: Check for RuntimeError instead of ComponentError in NamedEntityExtractor test

[julian-risch]

Related Issues

• Fixes NamedEntityExtractor e2e test fails when component has not been warmed up #7761

Proposed Changes:

• Check for RuntimeError instead of ComponentError

How did you test it?

Notes for the reviewer

I am not convinced there really is a need for an end-to-end test here. We're not testing the warm up of any of the other components with end-to-end tests. In my understanding it's also not a good end-to-end because it doesn't do more than initializing.
I suggest we merge this fix so that the end-to-end test runs through again. We can open a separate issue about making all the tests in the fail unit or integration tests and only keep test_ner_extractor_in_pipeline as e2e test.

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