samples: zbus: benchmark: complete refactoring and add msg subscriber to benchmark

[rodrigopex]

Note

This PR rewrites the whole benchmark sample to improve code reuse and macro calls.

The benchmark sample did not contemplate message subscribers. It adds the msg subscribers and improves the organization of the project.

[kartben]

some comments from my side -- fwiw it would help if the PR would be split in smaller chunks as there seems to be several changes here beyond just "adding message subscribers to benchmark", making the review more difficult than necessary. Thanks!

[rodrigopex]

@kartben

some comments from my side -- fwiw it would help if the PR would be split in smaller chunks as there seems to be several changes here beyond just "adding message subscribers to benchmark", making the review more difficult than necessary. Thanks!

Thank you for the comments. I am aware that it is better to separate the changes. However, it would take so long to be accepted. My PRs usually take three weeks or more to be added. If I split that into 3 PRs, it would take two months. I am trying my best here; the bigger PRs are more challenging to review. Yet, it makes my life easier. My baby boy, the Ph.D., and my work take almost all the time I have to contribute. I ask you folks for patience with my big PRs. As soon as things go lighter here, I will separate that. Sounds good?

[rodrigopex]

Add changes requested by @kartben.

[rodrigopex]

@kartben, is there anything I should change here to make that okay for merging?

[kartben]

@kartben

some comments from my side -- fwiw it would help if the PR would be split in smaller chunks as there seems to be several changes here beyond just "adding message subscribers to benchmark", making the review more difficult than necessary. Thanks!

Thank you for the comments. I am aware that it is better to separate the changes. However, it would take so long to be accepted. My PRs usually take three weeks or more to be added. If I split that into 3 PRs, it would take two months. I am trying my best here; the bigger PRs are more challenging to review. Yet, it makes my life easier. My baby boy, the Ph.D., and my work take almost all the time I have to contribute. I ask you folks for patience with my big PRs. As soon as things go lighter here, I will separate that. Sounds good?

Hi @rodrigopex -- I will try to find time to review this but to clarify I was not asking for several PRs but rather to try and isolate the changes in several commits (but all in the same PR of course), so that reviewing the changes is easier. Here it looks like a fairly significant refactoring intertwined with what might be some less impactful changes, and it would have been great to be able to review the former while only quickly looking at the latter.

[rodrigopex]

Changes requested have been attended, @fabiobaltieri.

[rodrigopex]

Changes requested have been attended, @fabiobaltieri.

[rodrigopex]

Thank you for reviewing that, guys. Let's keep going!