Print dangling messages from FileDescriptor

Previously we were only printing dangling messages if the FileDescriptor
had other messages or enums defined. Now we store/print them regardless.
This should have been the behavior before I just didn't have a valid
test case.

Fixes #58.
Merge pull request #58 from localshred/fix_empty_extended_file_58

Extensions are not compiling correctly