Add support for names rather than coordinates for Vizier.query_region

Currently one has to do the name--coordinate resolution outside of the module, would be nice if the method accepts name input (similarly `query_object()`).

However, the Sesame name resolution happens on the server side for `query_object()`, if passing object names via the API, then we can still build in a Simbad query before running the vizier one.

Start by comparing the Vizier.query_region and query_object entry points, then inspect how name resolution is handled for query_object and whether Simbad can be called before the Vizier request. Done means query_region accepts object names, resolves them consistently, and preserves the existing coordinate-query behavior; the issue does not name a test file.

Written by the indexing model from the issue text.