chore: Standardize Method Naming in Mapping Service

[ltalarcz]

📝 Description

This pull request standardizes function and method naming across the codebase by converting all function names from camelCase to snake_case. This improves code readability and aligns with Python's PEP 8 style guidelines. The changes affect the main API service, model interface, model implementation, mesh utilities, and service entry points.

API Service and Entry Point Standardization:

• All Flask route handlers, error handlers, and core API service functions in api_service_base.py have been renamed to use snake_case (e.g., healthCheck → health_check, runModelInference → run_model_inference, startApp → start_app). [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]
• The service initialization override in mapanything_service.py is updated to use the new initialize_model name. [1] [2]

Model Interface and Implementation:

• All abstract methods in model_interface.py are renamed to snake_case (e.g., loadModel → load_model, runInference → run_inference). [1] [2] [3] [4] [5] [6]
• Corresponding method implementations in mapanything_model.py are also renamed, including internal helpers and calls to these methods. [1] [2] [3] [4] [5] [6] [7]

Mesh Utility Functions:

• Utility functions in mesh_utils.py are renamed to snake_case (e.g., createPointcloudFromMesh → create_pointcloud_from_mesh, getMeshInfo → get_mesh_info). [1] [2]

These changes ensure consistency throughout the codebase and make the code easier to maintain and understand for all contributors.

✨ Type of Change

Select the type of change your PR introduces:

• 🐞 Bug fix – Non-breaking change which fixes an issue
• 🚀 New feature – Non-breaking change which adds functionality
• 🔨 Refactor – Non-breaking change which refactors the code base
• 💥 Breaking change – Changes that break existing functionality
• 📚 Documentation update
• 🔒 Security update
• 🧪 Tests
• 🚂 CI

🧪 Testing Scenarios

Describe how the changes were tested and how reviewers can test them too:

• ✅ Tested manually
• 🤖 Ran automated end-to-end tests

✅ Checklist

Before submitting the PR, ensure the following:

• 🔍 PR title is clear and descriptive
• 📝 For internal contributors: If applicable, include the JIRA ticket number (e.g., ITEP-123456) in the PR title. Do not include full URLs
• 💬 I have commented my code, especially in hard-to-understand areas
• 📄 I have made corresponding changes to the documentation
• ✅ I have added tests that prove my fix is effective or my feature works