Mqtt frames v8

[hsadia538]

• I have read the contributing guide lines at https://suricata.readthedocs.io/en/latest/devguide/codebase/contributing/contribution-process.html
• I have signed the Open Information Security Foundation contribution agreement at https://suricata.io/about/contribution-agreement/
• I have updated the user guide (in doc/userguide/) to reflect the changes made (if applicable)

Link to redmine ticket: https://redmine.openinfosecfoundation.org/issues/5731

Previous PR: #8508

Describe new changes:

• Add trunc.data frames to cater for truncated packets

suricata-verify-pr: 1123

[codecov]

Codecov Report

Merging #8540 (214ea8b) into master (d9e6301) will increase coverage by 0.07%.
The diff coverage is 79.13%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #8540      +/-   ##
==========================================
+ Coverage   81.84%   81.91%   +0.07%     
==========================================
  Files         967      967              
  Lines      278343   278480     +137     
==========================================
+ Hits       227799   228122     +323     
+ Misses      50544    50358     -186     

Flag	Coverage Δ
fuzzcorpus	64.09% <78.26%> (+0.15%)	⬆️
suricata-verify	59.82% <79.13%> (+0.16%)	⬆️
unittests	63.33% <1.73%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

[inashivb]

Following the discussion that happened privately, this data frame type does not seem to be necessary as we cannot annotate something that does not exist. Even if the data is truncated, the parsed parts can be tagged with Pdu, so, we can get rid of this. Make sure to add tests corresponding to truncated data. e.g.

aaaaaaaaaaaaaaabbbbbbbbbb 

where a..a == data exactly the length limit
b..b == extra data that should ideally be truncated by the parser.
So, you have three tests.

1. Well within the boundary.
   check for say first 4B of data in Pdu, it should match.
2. Boundary test. Should match.
   check for all aaaa exactly up to the length limit.
3. Post boundary test. Should not match.
   check for aaaa...bbb i.e. good data + truncated data

[hsadia538]

followed by #8730