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.
Check for dup field tags/names in define_field

The rprotoc generator is duped by duplicate field names when you extend
the same message from within different scopes:

message Foo {
  ...
}

message Bar {
  extend Foo {
    optional Protobuf::Field::Int32Field, :foo, 100
  }
}

message Baz {
  extend Foo {
    optional Protobuf::Field::Int32Field, :foo, 101
  }
}

The fix is simply to check on each Message.define_field call for fields
that already exist with the same name (regular or extension fields).

Fixes #70
move running up to avoid race condition of starting multiple workers and they die before server is "running"
bump to 2.7.8
add specs for binary encoding in strings and checking utf-8 keeps chars
bump to 2.7.9
Merge pull request #58 from localshred/fix_empty_extended_file_58

Extensions are not compiling correctly
Merge branch '2-7-stable'
Add back in ResourceService implementation for spec
Use dup instead of deep_dup
Merge pull request #87 from localshred/70_duplicate_ext_fields

Check for dup field tags/names in define_field
Merge pull request #88 from localshred/remove_deep_dup

Use dup instead of deep_dup
Add back in ResourceService implementation for spec
Update gitignore
Bump version 2.7.10
Remove multi-field definitions for specs to pass
Merge branch '2-7-stable'
Merge origin/master into instantiate_runner_and...

Conflicts:
	lib/protobuf/rpc/servers/zmq/server.rb