Fixes # .

Summary/Motivation:

This PR is a significant overhaul of the utilities for converting ConfigDict objects unto numpydoc documentation strings. This was motivated by #3641, where it was pointed out that it is difficult / impossible to cleanly document CONFIG class attributes and nested ConfigDict objects.

This PR demonstrates the new use / formatting using the NLWriter and the contrib.solver Ipopt interface. Promulagating it to the rest of the solvers / transformations is left for a future PR.

Changes proposed in this PR:

• Move the detailed (explanation) documentation of the Config system into the RST file (prevents duplicate labels / references
• Add new decorators:
  • @document_configdict for documenting classes derived from ConfigDict
  • @document_class_CONFIG for documenting CONFIG class attributes (and optionally, methods that use CONFIG for keyword argument resolution
• monkeypatch Sphinx so that non-class domain validators are correctly linked in the documentation.
• Update the numpydoc formatter:
  • reference (do not recurse into) nested ConfigDict if the ConfigDict is documented separately (either through @document_configdict or @document_class_CONFIG)
  • Avoid unused (and unneeded) dict object in ConfigDict domain
• Rework the Executable and Library factories to be true singletons; support their use as domains in ConfigValue
• Convert repn.plugins.nl_writer and contrib.solver.solvers.ipopt to the new system (as demonstrators / test cases).

Legal Acknowledgement

By contributing to this software project, I have read the contribution guide and agree to the following terms and conditions for my contribution:

1. I agree my contributions are submitted under the BSD license.
2. I represent I am authorized to make the contributions and grant the license. If my employer has rights to intellectual property that includes these contributions, I represent that I have received permission to make contributions and grant the required license on behalf of that employer.