Rename MLBlock -> MLPipelineStep

[micahjsmith]

That's it :)

[csala]

Hi @micahjsmith I agree that the "block" name usage can be a bit confusing within the scope of a pipeline.
However, an MLBlock is thought as an independent block of code that can also be executed on its own, outside of the pipeline scope.

The whole rationale of the project naming is:

• An MLBlock is just a wrapper around a third party block of code, which provides it a uniform interface suitable for Machine Learning contexts. This is the core concept of the library.
• The MLBlocks library is called like that because its core concept is being able to create precisely that: instances of the MLBlock class.
• Eventually, we provide the MLPipeline, which allows to easily combine multiple MLBlock instances in the form of a pipeline. This, of course, ends up being a very important concept in the project, but it still revolves around the MLBlock concept.

So, here is my proposal: Let's keep the MLBlock class name, but rename the block concept inside the pipeline to steps.

This way, the MLPipeline will be composed of multiple steps, which inherently have an execution order, and it just happens that each one of these steps is an instance of an MLBlock class.

Does this sound right?