Move builtin_frames to a subpackage

This looks like a lot, but it's actually just moving the classes in ``builtin_frames.py`` to separate modules in a new package named ``builtin_frames``.  But the ``__init__.py`` of the new package imports them all back in, so it should be essentially a no-op in terms of the API as seen from the ``astropy.coordinates`` level.

This is intended to pave the way for adding new systems without having ``builtin_frames.py`` explode to an unmaintainable size.  I was going to do this as part of an upcoming ICRS<-> AltAz PR, but I figured it would be better to do this separately so that the diff is more readable in the new one.

@astrofrog @adrn @Cadair - this shouldn't disrupt anything in the API *unless* somewhere someone is assuming something about frame classes or their transformation functions have full-qualified names like ``astropy.coordinates.builtin_frames.*`` instead of ``astropy.coordinates.builtin_frames.<somemod>.*``.  I'm thinking that should be fine, but wanted to make sure there isn't some subtle assumption SunPy is making this might break.
class -> classes