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.11%. Comparing base (d60c699) to head (3c9b754).

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #1659      +/-   ##
==========================================
- Coverage   83.11%   83.11%   -0.01%     
==========================================
  Files         277      277              
  Lines       48207    48206       -1     
  Branches    10192     9925     -267     
==========================================
- Hits        40069    40066       -3     
- Misses       7243     7246       +3     
+ Partials      895      894       -1     

Flag	Coverage Δ
alpine320	75.10% <ø> (-0.01%)	⬇️
fedora40	75.12% <ø> (-0.04%)	⬇️
macos-13	80.62% <ø> (ø)
macos-14	80.62% <ø> (+<0.01%)	⬆️
macos-15	80.59% <ø> (ø)
mingw32	70.83% <ø> (-0.04%)	⬇️
mingw64	70.79% <ø> (-0.04%)	⬇️
npcap	85.24% <ø> (-0.02%)	⬇️
rhel94	74.97% <ø> (-0.01%)	⬇️
ubuntu2004	58.59% <ø> (+<0.01%)	⬆️
ubuntu2004-zstd	58.68% <ø> (+<0.01%)	⬆️
ubuntu2204	74.89% <ø> (-0.01%)	⬇️
ubuntu2204-icpx	61.45% <ø> (ø)
ubuntu2404	75.17% <ø> (+0.01%)	⬆️
unittest	83.11% <ø> (-0.01%)	⬇️
windows-2019	85.27% <ø> (-0.01%)	⬇️
windows-2022	85.30% <ø> (-0.01%)	⬇️
winpcap	85.26% <ø> (ø)
xdp	50.53% <ø> (-0.01%)	⬇️

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 .