Standardize documentation showing module import path and example

[zacharybinger]

Description

Importing models isn't the most obvious to new users. If you look at the documentation there isn't anything to indicate what the module name is and if you look in the code

@declare_process_block_class("ReverseOsmosis1D")
class ReverseOsmosis1DData(ReverseOsmosisBaseData):
    """Standard 1D Reverse Osmosis Unit Model Class."""

it isn't obvious unless you understand what the wrapper is doing (i.e. ReverseOsmosis1DData vs. ReverseOsmosisBaseData vs. ReverseOsmosis1D)

Motivation

Reduce the learning curve of WaterTAP and make the documentation more clear

Possible Implementation

Additional Context

No response

[adam-a-a]

One thought-- should we consider a landing page with a table of all unit models and associated import lines? Having it all in one place would be convenient.

[ksbeattie]

This is a really good example for new developers to the project to get experience on opening a PR. It's a pretty straightforward change and there will need to be many of them all across the documentation.