Fix: torch >= 2.6 compatibility & multi-instance file contention

[andylin-hao]

This PR fixes LIBERO's compatibility with torch>=2.6 by adding weights_only=False to torch.load, which is a breaking change in torch 2.6 that denies any other data structures besides tensor, primitives, and dictionary. See https://docs.pytorch.org/docs/stable/notes/serialization.html#weights-only

When running LIBERO on torch 2.6, the following error occurs:

File "/opt/libero/libero/libero/benchmark/__init__.py", line 164, in get_task_init_states
    init_states = torch.load(init_states_path)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/venv/openvla/lib/python3.11/site-packages/torch/serialization.py", line 1470, in load
    raise pickle.UnpicklingError(_get_wo_message(str(e))) from None
_pickle.UnpicklingError: Weights only load failed. This file can still be loaded, to do so you have two options, do those steps only if you trust the source of the checkpoint.
    (1) In PyTorch 2.6, we changed the default value of the `weights_only` argument in `torch.load` from `False` to `True`. Re-running `torch.load` with `weights_only` set to `False` will likely succeed, but it can result in arbitrary code execution. Do it only if you got the file from a trusted source.
    (2) Alternatively, to load with `weights_only=True` please check the recommended steps in the following error message.
    WeightsUnpickler error: Unsupported global: GLOBAL numpy.core.multiarray._reconstruct was not an allowed global by default. Please use `torch.serialization.add_safe_globals([_reconstruct])` or the `torch.serialization.safe_globals([_reconstruct])` context manager to allowlist this global if you trust this class/function.

After adding the weights_only argument, the states can be correctly loaded and LIBERO can run on torch >= 2.6. Supposedly, this addresses #99.

Further more, when running multiple processes using LIBERO for the first time, all the processes try to create the config directory and file simultaneously, causing contention.
For example, several processes may find that the config directory does not exist, and try to create it together. Only one process will succeed while the others crash directly due to folder already exists.

This PR adds file lock to prevent such contention, thereby enabling LIBERO to be used in large parallel training.

[Lorenzo-Mazza]

Is there any plan to merge this? I think having python fixed to 3.8 is not a realistic thing for many people in almost 2026...Python 3.8 reached its official EOL in October 2024, thus it would be nice for the robotics community to use benchmarks with up-to-date tools.