Reformat Packet++ documentation to use triple-slash doxygen format.

[Dimi1010]

Part of #1658
Includes reformatting of classes, structs and namespace documentation.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.58%. Comparing base (2ae8837) to head (7705b5a).
Report is 2 commits behind head on dev.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #1659      +/-   ##
==========================================
+ Coverage   83.13%   83.58%   +0.45%     
==========================================
  Files         279      275       -4     
  Lines       48395    47762     -633     
  Branches    10500    10101     -399     
==========================================
- Hits        40231    39922     -309     
+ Misses       7044     6786     -258     
+ Partials     1120     1054      -66     

Flag	Coverage Δ
alpine320	75.09% <ø> (-0.01%)	⬇️
fedora40	75.12% <ø> (-0.04%)	⬇️
macos-13	80.61% <ø> (+<0.01%)	⬆️
macos-14	80.61% <ø> (+<0.01%)	⬆️
macos-15	80.58% <ø> (ø)
mingw32	70.80% <ø> (-0.04%)	⬇️
mingw64	70.79% <ø> (-0.02%)	⬇️
npcap	85.21% <ø> (-0.02%)	⬇️
rhel94	75.01% <ø> (+0.03%)	⬆️
ubuntu2004	58.62% <ø> (+0.03%)	⬆️
ubuntu2004-zstd	58.71% <ø> (+<0.01%)	⬆️
ubuntu2204	74.89% <ø> (-0.01%)	⬇️
ubuntu2204-icpx	61.27% <ø> (ø)
ubuntu2404	75.13% <ø> (-0.04%)	⬇️
unittest	83.58% <ø> (+0.45%)	⬆️
windows-2019	85.24% <ø> (-0.01%)	⬇️
windows-2022	85.27% <ø> (-0.01%)	⬇️
winpcap	85.24% <ø> (ø)
xdp	?

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Dimi1010]

Ok, minor issue with the reformatting.
There are some @verbatim blocks that don't like working well with the /// format, and I am not sure how to deal with that...
The issues are that I am unsure if the /// will show in the actual verbatim text and the /// block needs to be unbroken with those lines to count as a single block. Also, I am getting a parser error in the SSLLayer so the parser may also be getting confused.

So unless anyone has ideas, I guess, we have 3 options.

• Use the /** */ style for those sections.
• Remove the verbatim blocks (undesirable imo, because they are helpful)
• Call it a day, revert the other 2 refactor PRs (Reformat Pcap++ documentation to use triple-slash doxygen format. #1660, Reformat Common++ documentation to use triple slash. #1647) and continue with the old /** */ format. There haven't been many changes to the documentation yet, so the revert should be mostly clean if needed.

cc: @seladb @tigercosmos

[Dimi1010]

Discontinued due to issues with doxygen parsing of verbatim example blocks.

[Dimi1010]

Fix seems to work. Thanks @egecetin .