Eliminated code redundancy with find_planet_row() method and added SIMBAD alias support

Two significant changes with this update.

1. Up till now, two methods (get_properties() and find_neighbors()) were both using virtually identical code, and when I made changes they really needed to be applied in both places. This was terribly confusing and inefficient. Now that code is housed in the new find_planet_row() method, which queries the planet lists to identify the appropriate row where the target planet lives.
   
2. Utilizing the new find_aliases method, the user can now identify the planet in the TESS catalog using any valid SIMBAD identifier (TIC support and TOI support still not yet available but coming soon!). This is important because it’s not always obvious to the user which name a planet may be listed under (although you can probably guess in most cases).
   
   For example: If I want to download the light curve for TOI-101.01, I cannot (yet!) use TOI-101 as my targetID. Instead, I will need to use it’s more famous name, WASP-46 (or WASP-46b). But suppose your target has other names, too? You can use any of them if they’re listed in SIMBAD. For example, WASP-46 also goes by the catchy nom de plume “2MASS J21145687-5552184”. Before if you typed this in you would have received an error. No more! Now, if you really want to type that whole thing in (or, more likely, you’re feeding in a list of star IDs), MoonPy will utilize the find_aliases() method to dig through all known aliases until it finds the moniker cataloged in the… catalog. That is, WASP-46.