ctpdev: raw decoder output size protection

[lietava]

I put protection size as parameter which can be tuned on data.

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass
async-2023-pp-apass1
async-2022-pp-apass6
async-2022-pp-apass4
async-mc
async-data

[lietava]

HI @shahor02 , I added protection as parameter so I can tune it with data and can be fully swicthed off. Please, let me know your comments.

[shahor02]

@lietava I thought you wanted to cut on the raw data size before decoding. But this also looks fine.
At the moment you just log an error, I guess you should count a certain number of consecutive TFs with this error and then produce Fatal?

[lietava]

@shahor02 : thanks. Yes, one can cut also on raw input. Anyway I would start like this - just one frame maybe enough for 40 mhz ringing - and test with raw or directly in P2.

[lietava]

PLease, merge