Fixed documentation strings so the docs site can build

[yougotwill]

• When we have a constexpr the documentation builder still expects the docstring to have Inputs: None. We should probably update the script

// Fails

/// API: encrypt/ENCRYPT_DATA_OVERHEAD
///
/// This value contains the constant amount of extra bytes required for encryption as performed by
/// `encrypt()`/`decrypt()`/`encrypt_inplace()`/`decrypt_inplace()`.
///
/// That is, for some message `m`, encrypt_overhead() is the difference between m.size() and
/// encrypt(m).size().
constexpr size_t ENCRYPT_DATA_OVERHEAD = 40;  // ABYTES + NPUBBYTES

// Passes

/// API: encrypt/ENCRYPT_DATA_OVERHEAD
///
/// This value contains the constant amount of extra bytes required for encryption as performed by
/// `encrypt()`/`decrypt()`/`encrypt_inplace()`/`decrypt_inplace()`.
///
/// That is, for some message `m`, encrypt_overhead() is the difference between m.size() and
/// encrypt(m).size().
///
/// Inputs: None
///
constexpr size_t ENCRYPT_DATA_OVERHEAD = 40;  // ABYTES + NPUBBYTES

• When we write a function docstring we don't account for more complex typings such as <const unsigned char>. The regex for RPC_START in the build script does not account for spaces. I tried tweaking it but it broke other things. So this is the current solution which I have seen elsewhere in the code base.

// Fails

/// API: base/ConfigBase::DictFieldProxy::operator=(std::span<const unsigned char>)

// Passes

/// API: base/ConfigBase::DictFieldProxy::operator

[jagerman]

I opened #45 as an alternative to this that fixes the issues in the parser.

[jagerman]

This is caused by missing /// Member variable. (fixed in #45)

[jagerman]

Likewise

[jagerman]

This one is indeed a parser problem; I've added a change in #45 that recognizes this as a constant automatically, but also adds a new /// Constant. stanza in cases where the constant might be too complex.