fix: use loopback flight location by default - #427

Summary

• change the default Flight location host from 0.0.0.0 to 127.0.0.1
• add a regression check for the default create_location() host
• keep this scoped to the PyArrow Flight failure class from Windows-local tox failures: CP949 decode, SQLite temp-file lock, PyArrow Flight 0.0.0.0 #424

On Windows, tests/test_core/test_flight/test_flight_server.py::TestFlightServerIntegration::test_server_operations failed before this change because the client tried to connect to grpc://0.0.0.0:<port>, which produced WSA Error 10049. 0.0.0.0 is useful as a bind-all address, but it is not a portable client target.

This follows #426 and intentionally leaves the SQLite temp-file lock class from #424 separate.

Tests

• .venv\Scripts\python.exe -m pytest tests\test_core\test_flight\test_flight_server.py -q
• .venv\Scripts\python.exe -m pytest tests\test_core\test_artifacts\test_artifacts.py::TestBaseArtifacts::test_basic_artifact_feature -q
• .venv\Scripts\python.exe -m pytest tests\test_plugins\compute_framework\base_implementations\sqlite -q
• .venv\Scripts\ruff.exe format --check mloda\core\runtime\flight\flight_server.py tests\test_core\test_flight\test_flight_server.py
• .venv\Scripts\ruff.exe check mloda\core\runtime\flight\flight_server.py tests\test_core\test_flight\test_flight_server.py

Part of #424.