Allow API documentation to be built directly from Doxygen

[pniedzielski]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Our current API documentation was generated using bde-tools's bdedox executable. Since our comments are no longer in BDE-style, running doxygen on the codebase does not pick up several things our current published API docs have, like package group, package, and component-level documentation, some BDE formatting, and \brief descriptions automatically generated from the first sentence of a documentation comment.

Additionally, some BDE-style documentation failed to convert, as in the bmqa_abstractsession component.

Expected Behavior

Running doxygen on the codebase should produce up-to-date documentation, including all our package group, package, and component documentation, and should support Doxygen-style annotations, such as \deprecated and \par.

Steps To Reproduce

1. Run doxygen on the codebase.
2. Compare the output to the public API documentation.

BlazingMQ Version

HEAD

Anything else?

No response

[chrisbeard]

Non-exhaustive to-do list for this effort:

1. convert group and package docs in mwc to doxygen format like bmqa
2. convert group and package docs in mqb to doxygen format (less important)
3. add make doc target that at least generates bmq and mwc docs
4. make the CI run this on release tags and upload it to the website
5. go through and find places where the doxygen conversion failed to properly convert BDE style to doxygen style
6. use doxygen tags for things like @deprecated