ENH: turning off old simbad API

While we're looking at the code with @keflavich we noticed that we have `raise_for_status` in the code for 6 years now, so we feel it would be a way for giving feedback to all the users that they need to upgrade to a newer version; basically almost everyone is using a version where a http error is being captured early on and raised.

cc @ManonMarchand once she is back.

Start by locating the SIMBAD API implementation and the existing raise_for_status handling mentioned in the issue. Review how HTTP errors currently reach users and determine the project-approved behavior for users on older versions. Done should be defined as the old API path being turned off with clear upgrade feedback, but the issue does not name files or tests.

Written by the indexing model from the issue text.