Adjust get_type() method for pipelines

[vblagoje]

Related Issues

• partially resolves Improve pipeline telemetry #3342

Proposed Changes:

get_type() misclassified some pipelines as "Unknown pipeline". These pipelines are now properly classified by type.

How did you test it?

Unit test, see PR diff

Notes for the reviewer

Any other test cases from telemetry?

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 tests that demonstrate the correct behavior of the change
• I've used the conventional commit convention for my PR title
• I documented my code
• I ran pre-commit hooks and fixed any issue

[vblagoje]

@julian-risch I added several tests that now correctly return the right pipeline type instead of "Unknown pipeline." Now we rely on types of objects to deduce the pipeline type rather than names which were not standardized to begin with. Please have a look.

[julian-risch]

Looks good to me! 👍 This is a nice improvement of what we had before. I don't see a need for adding test cases for all the different pipeline types. From my point of view the test that you added is sufficient.
The only point I was thinking about is the TranslationWrapperPipeline. If a pipeline contains two BaseTranslator components we would now know that it is a TranslationWrapperPipeline but we wouldn't know what else is in the pipeline (DocumentSearch, ExtractiveQA, etc.). However, it's okay that way. We still have the detailed list of components if more details are needed.