Fix changing simbad config items at runtime

[eerovaher]

Previously changing simbad config items at runtime had no effect. Now the config items are read when they are needed, unless the user has specified the corresponding class or instance variable, in which case the latter takes precedence.

Relevant for #2291

[codecov]

Codecov Report

Attention: Patch coverage is 95.23810% with 1 line in your changes missing coverage. Please review.

Project coverage is 63.01%. Comparing base (0883e92) to head (0f6a310).
Report is 1525 commits behind head on main.

Files with missing lines	Patch %	Lines
astroquery/simbad/core.py	95.23%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2292      +/-   ##
==========================================
+ Coverage   62.99%   63.01%   +0.01%     
==========================================
  Files         133      133              
  Lines       17291    17300       +9     
==========================================
+ Hits        10892    10901       +9     
  Misses       6399     6399              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[keflavich]

I like this solution. @bsipocz I'm holding off on pressing merge so you can have a look, but I think this could serve as the template for other modules moving forward.

I would also like to see these parameters also be specifiable at instance creation time, but that can be a conversation on a different thread.

[eerovaher]

I had to rebase to solve a conflict in the change log.

[eerovaher]

I had to rebase again to resolve another merge conflict in the change log.

I also decided to add a _row_limit property that works analogously to the other two I had added earlier. The main reason I added the properties was to avoid code duplication and adding a property for row limit was not needed for that. But for consistency and simplicity it is better if there are properties for all the config items.

[bsipocz]

I would like to get this change done in the same release for a bunch of the modules (at least the ones that are most often used), and maybe also add the warning #638 suggest (there is one already in mast.missions), so would push this to the next release.
The plan is to get that out reasonably quickly, and the plan also includes quite a few backend changes, e.g. caching, cloud access, etc, so this would perfectly fit in there.

[eerovaher]

I have rebased the commits to update the change log entry.

[eerovaher]

For some reason none of the tests ran at all. Should I rebase again to start the tests?

[eerovaher]

I've updated the pull request so that the documentation about the Simbad subpackage is kept up to date regarding the configuration, and I had to rebase to resolve a merge conflict in the change log.

[eerovaher]

I had to rebase to fix a merge conflict in the change log, again.