Consider removing the `parse_` iotools functions

[kandersolar]

The read_ and parse_ iotools functions are largely redundant; read_ is a simple wrapper around parse_. It has been suggested to remove the parse_ functions and have read_ work with both file-like objects and filenames/URLs.

@AdamRJensen in #2326 (comment):

I think we should get rid of the parse functions which will significantly reduce duplicated documentation (if anything then make the parse functions private with little documentation).

and @wholmgren in #2378 (comment):

Are we also going to add support for buffers to read_nsrdb_psm4? I recommend moving forward with this PR API as is and if you want to take that on before the next release then go for it.

Also need to edit the docstring returns sections if this function becomes private.

I am +1 to getting rid of parse_. There is some discussion back in #842 that may be of interest.

If we go ahead with this, we should start with the parse_ function in pvlib.iools.psm4, as it has not been included in a release yet and thus does not need a deprecation period.

[AdamRJensen]

I guess the first step would be to mark the parse_ as deprecated and then come back and remove once a major version or two has passed?

[echedey-ls]

X referencing #2396 , it should be updated accordingly

[AdamRJensen]

X referencing #2396 , it should be updated accordingly

I have added it to the deprecation tracker.

[AdamRJensen]

Closing this issue as all parsing functions have been deprecated as of v0.13.0. Remaining tasks are in the deprecation tracker and in #2469.