Rename from_gltf_bytes to load_gltf_from_bytes (#567)

Summary:
Pull Request resolved: #567

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 first 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}], since this is the format most of the other functions use.

Reviewed By: jeongseok-meta

Differential Revision: D82386701

fbshipit-source-id: ad93adbf66bddf7a8de0656b66a53d44cf1b3237

Author: cdtwigg

pymomentum/geometry/geometry_pybind.cpp

@@ -235,7 +235,7 @@ PYBIND11_MODULE(geometry, m) {
   // - load_model_definition_from_bytes(model_bytes)
   //
   // [static methods for io]
-  // - from_gltf_bytes(gltf_btyes)
+  // - load_gltf_from_bytes(gltf_btyes)
   // - to_gltf(character, fps, motion, offsets)
   // - load_fbx(fbxFilename, modelFilename, locatorsFilename)
   // - load_fbx_from_bytes(fbx_bytes, permissive)
@@ -668,7 +668,7 @@ Note that not all parameters will have limits; for those parameters (such as glo
 
 Note: In practice, most limits are enforced on the model parameters, but momentum's joint limit functionality permits applying limits to joint parameters also as a conveninence.  )")
       .def_static(
-          "from_gltf_bytes",
+          "load_gltf_from_bytes",
           &loadGLTFCharacterFromBytes,
           py::call_guard<py::gil_scoped_release>(),
           R"(Load a character from a gltf byte array.