Rustfmt 3836 v4

[catenacyber]

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

Describe changes:

• format rust code

#10088 with rebase

@jasonish if I understand correctly, the question with this is if the C code should be formatted within the same commit than rust, what do you think ?

[codecov]

Codecov Report

Attention: 383 lines in your changes are missing coverage. Please review.

Comparison is base (244a35d) 73.31% compared to head (d95abeb) 82.38%.
Report is 25 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #10303       +/-   ##
===========================================
+ Coverage   73.31%   82.38%    +9.06%     
===========================================
  Files         895      978       +83     
  Lines      148215   273112   +124897     
===========================================
+ Hits       108666   225006   +116340     
- Misses      39549    48106     +8557     

Flag	Coverage Δ
fuzzcorpus	63.81% <86.19%> (+0.33%)	⬆️
suricata-verify	61.69% <77.90%> (+0.16%)	⬆️
unittests	62.69% <34.77%> (?)

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

[jasonish]

@jasonish if I understand correctly, the question with this is if the C code should be formatted within the same commit than rust, what do you think ?

Maybe, or in the same batch. I've scripted a rustfmt into my scripts re-org/reformat of the C code as well.. Separate commit, but same batch. With the idea being that squash could be done just prior to merge.

[suricata-qa]

WARNING:

field	baseline	test	%
	SURI_TLPR1_stats_chk
.memcap_pressure	57	53	92.98%
.http.memuse	373800	404520	108.22%

Pipeline 18070

[catenacyber]

Will rebase when asked