Rename from_gltf_bytes_with_motion to load_gltf_with_motion_from_bytes (#568)

Summary:
Pull Request resolved: #568

This was actually feedback when I first landed this function, but I never got around to it.  However I recently noticed that there's a ton of inconsistency across these IO functions so let's unify them.

This is the second in a series of changes to make IO function naming more consistent across pymomentum. The naming pattern we're following is: {action}_{format}[_{data_type}][_{source_type}]

Reviewed By: jeongseok-meta

Differential Revision: D82386793

fbshipit-source-id: 76e6a0a947e76f60b05a7b251b50b24dddbd94c7

Author: cdtwigg

pymomentum/geometry/geometry_pybind.cpp

@@ -678,10 +678,10 @@ Note: In practice, most limits are enforced on the model parameters, but momentu
       )",
           py::arg("gltf_bytes"))
       .def_static(
-          "from_gltf_bytes_with_motion",
+          "load_gltf_with_motion_from_bytes",
           &loadGLTFCharacterWithMotionFromBytes,
           py::call_guard<py::gil_scoped_release>(),
-          R"(Load a character from a gltf byte array.
+          R"(Load a character and motion from a gltf byte array.
 
   :param gltf_bytes: A :class:`bytes` containing the GLTF JSON/messagepack data.
   :return: a valid :class:`Character`.