feat(components): get clproto message type from attribute

[domire8]

Description

One thing that has come to my attention with the recent documentation efforts and webinars is that the fact that we require the user to know the mapping between state representation type and the clproto message type when adding an output in python is a bit too much. I propose here in a non breaking fashion to remedy that by getting the clproto message type from the type of the class attribute. The functionality stays exactly the same (e.g. existing code still works and if a user wants to publish a CartesianPose as a CARTESIAN_STATE_MESSAGE, that is still possible), but for the simple case of the 1:1 mapping, the clproto message type is not required anymore to add an output.

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]

great idea, looks good to me. I would probably take a few moments to test, but I from what I see the tests cover it, so go for it if you are satisfied with it (after the CHANGELOG update).

[eeberhard]

Very clever, nice idea! This will be convenient for users.

One small discussion point and needs changelog of course.