Rename ``.ReplacementTransform`` and ``.Transform`` to minimize confusion.

[JasonGrace2282]

Oftentimes people will get confused as to the difference between ReplacementTransform and Transform due to their similar names. It might be beneficial to rename them to something else.
After brainstorming, some possible names for ReplacementTransform are:

• Become
• Replace

and for Transform:

• ShapeShift
• Morph

My personal favorite is Morph ;)

What do you think? It would be nice to have as many opinions as possible since these animations are very commonly used.
CC @chopan050

You can read the original conversation starting here

[Nikhil-42]

I personally like Become and Morph. We just have to make sure that Become has the same behavior as Mobject.become.

[ubaldot]

Oh great! I haven't seen this. I also opened a similar discussion on the help forum on discord one minute ago. :/

[chopan050]

Another option could be TransformThenReplace or MorphThenReplace for ReplacementTransform.
Using Become might create a confusion with Mobject.become(), although I'd vote for renaming that method to Mobject.morph_into(), because it makes more explicit that the Mobject is changing its shape and color to match a 2nd Mobject, without actually being that 2nd object.