detect/analyzer: add more details for the xbits keyword.

[kaddujames501-ship-it]

Task #6351

Contribution style:

• I have read the contributing guide lines at
  https://docs.suricata.io/en/latest/devguide/contributing/contribution-process.html

Our Contribution agreements:

• I have signed the Open Information Security Foundation contribution agreement at
  https://suricata.io/about/contribution-agreement/ (note: this is only required once)

Changes (if applicable):

• I have fixed a ticket at
  https://redmine.openinfosecfoundation.org/projects/suricata/issues

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

Describe changes:
Add xbits keyword details to engine analysis output in DumpMatches function. Exposes cmd, name, track, and expire properties in JSON format, following the same pattern as byte_jump and flowbits.

This improves the engine analysis report by providing complete information about xbits usage in rules when running with --engine-analysis flag.

Provide values to any of the below to override the defaults.

• To use a Suricata-Verify or Suricata-Update pull request,
  link to the pull request in the respective _BRANCH variable.
• Leave unused overrides blank or remove.

SV_REPO=
SV_BRANCH=github.com/OISF/suricata-verify/pull/2741
SU_REPO=
SU_BRANCH=

James Kaddu: [email protected]

[github-actions]

NOTE: This PR may contain new authors.

[codecov]

Codecov Report

❌ Patch coverage is 0% with 37 lines in your changes missing coverage. Please review.
✅ Project coverage is 84.13%. Comparing base (cdd4ea0) to head (c20cb6a).

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #14252      +/-   ##
==========================================
- Coverage   84.14%   84.13%   -0.02%     
==========================================
  Files        1013     1013              
  Lines      262313   262350      +37     
==========================================
- Hits       220733   220732       -1     
- Misses      41580    41618      +38     

Flag	Coverage Δ
fuzzcorpus	63.30% <0.00%> (-0.03%)	⬇️
livemode	18.71% <0.00%> (-0.06%)	⬇️
pcap	44.57% <0.00%> (+<0.01%)	⬆️
suricata-verify	64.85% <0.00%> (-0.03%)	⬇️
unittests	59.18% <0.00%> (-0.01%)	⬇️

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jufajardini]

Hello, thanks for this contribution. Could you please create SV tests to go with this patch? You can check OISF/suricata-verify#2717 for an overall idea of what type of test we are looking for, for these engine analysis tasks :)

[jufajardini]

Something happened with the commit message: the ticket number is aaaaaalll the way lost to the right :P

This looks good, but will be easier to judge once we have the SV test, so I'm marking it as changes requested, for the SV tests, and the commit message.

[kaddujames501-ship-it]

Hello, thanks for this contribution? Could you please create SV tests to go with this patch? You can check OISF/suricata-verify#2717 for an overall idea of what type of test we are looking for, for these engine analysis tasks :)

the PR is here as requested github.com/OISF/suricata-verify/pull/2741

[kaddujames501-ship-it]

Something happened with the commit message: the ticket number is aaaaaalll the way lost to the right :P

This looks good, but will be easier to judge once we have the SV test, so I'm marking it as changes requested, for the SV tests, and the commit message.
the commit message has now been catered for. thanks for the corrections