Eliminate xya2pts from data_manager and use load mesh functionality instead

[ole]

Affected files development/okushiri_2005/lwru2.py:from pyvolution.data_manager import xya2pts development/okushiri_2005/lwru2.py:xya2pts(project.bathymetry_filename, verbose = True, inundation/debug/mesh_error_reporting/show_mesh_bug.py:from pyvolution.data_manager import xya2pts inundation/debug/mesh_error_reporting/show_mesh_bug.py:xya2pts(filenames.bathymetry_filename, verbose = True, inundation/pyvolution/data_manager.py:def xya2pts(basename_in, basename_out=None, verbose=False, production/merimbula_2005/prepare.py: from pyvolution.data_manager import xya2pts production/merimbula_2005/prepare.py: xya2pts(project.bathymetry_filename, verbose = True)

There are some file types that have the same information, but can be written in different formats. This are points files that can be pts(binary) or xya(ascii) and mesh files, that can be msh(binary) or tsh(ascii).

All interfaces that use points or mesh files should be able to deal with both formats.

This makes an xya2pts function redundant in most cases. Maybe it can be used for testing the points interface, to make sure that it can handle both binary or ASCII? That functionality is tested in the ?import_points_file? function.