Rewrite docstrings to facilitate API reference generation

[alexhroom]

cf. RascalSoftware/RAT-Docs#1 ; if API reference is autogenerated, then some kind of docstring formatting convention should be used to improve the way it is formatted in the documentation. This can be in the RST docstring style, or the Numpy or Google style (and we can then use the Sphinx extension napoleon to convert)

[StephenNneji]

We have agreed to use the numpy style to be consistent with Python API and RasCAL

[StephenNneji]

The user facing functions should be priority for docstring refactoring. This should help keep track of what's left and who is doing what

• RAT.API.projectClass.backgroundsClass
• RAT.API.projectClass.baseContrasts Adds docstring for contrasts and some refactors #389
• RAT.API.projectClass.contrastsClass Adds docstring for contrasts and some refactors #389
• RAT.API.projectClass.customFileClass
• RAT.API.projectClass.dataClass
• RAT.API.projectClass.domainContrastsClass Adds docstring for contrasts and some refactors #389
• RAT.API.projectClass.domainsClass Adds docstring for contrasts and some refactors #389
• RAT.API.projectClass.layersClass
• RAT.API.projectClass.multiTypeTable Adds docstrings for main calculation and multiTypeTable #392
• RAT.API.projectClass.parametersClass
• RAT.API.projectClass.projectClass
• RAT.API.projectClass.resolutionsClass
• RAT.API.projectClass.tableUtilities
• RAT.API.createProject
• RAT.API.RAT
• RAT.API.RATMain Adds docstrings for main calculation and multiTypeTable #392
• RAT.API.controlsClass
• RAT.API.enums Adds docstrings to enums #391
• RAT.targetFunctions.reflectivityCalculation Adds docstrings for main calculation and multiTypeTable #392

[DrPaulSharp]

Can this issue now be closed?