fix(components): try catch subscription callbacks

[domire8]

Description

This PR improves the robustness of the component interfaces by try catching subscription callbacks in all cases. Until now, we "only" try catched additional user callbacks.

One might argue that we should only catch CoreException and not all exceptions as the user might want to throw exceptions on purpose but I can not imagine a setup where one would desire to throw an exception in a subscription callback.

Also, we could put the component in error state by putting the raise_error there but that as well, I'm just not sure if I want to introduce it, since we'd have to do that consistently in all the add_input variants. I like the idea of subscription callbacks just failing with a throttled log instead of raising the error on the component.

Review guidelines

Estimated Time of Review: 5 minutes

Checklist before merging:

• Confirm that the relevant changelog(s) are up-to-date in case of any user-facing changes

[bpapaspyros]

Good addition indeed, just a suggestion on how we could perhaps address this

[bpapaspyros]

Looks good! thanks for adding the tests, I missed them in the previous review

[eeberhard]

I agree this is a nice thing for now to prevent unhandled exceptions. We can think about additional user requirements from there, but a user could also raise_error manually from within their callback so I think it's already quite good!