Fix Intel compiler warnings in include files on Windows

Check in strong name key.

Added support for binary gems.

Few fixes.

Enable JavaScript tests for binary parse/serialize.

Rename Preconditions to ProtoPreconditions

(Generated code changes in next commit.)

Rename GeneratedCodeInfo to GeneratedClrTypeInfo

Recently, descriptor.proto gained a GeneratedCodeInfo message, which means the generated code conflicts with our type.
Unfortunately this affects codegen as well, although this is a part of the public API which is very unlikely to affect hand-written code.

Generated code changes in next commit.

Clarify readme for C#

These should have been included in the first match
but I overlooked them.

This involved deleting some of the code that tests
Google-internal-only features.

Make protobuf Skylark extension appends the workspace root

Manually down-integrate python JSON struct support from internal code base.

Integrate google internal changes to master

Java files are moved to un-do the hack in the prevous commit, which
moved the java files to the original position for integration.

Moving the files to their original location, so that opensource changes
can be picked during the internal merge. Those files will be moved into
the correct location after merging with internal code.

Note: do NOT merge this into master without the other internal
down-integration commit.

Ensure that FieldMask, Timestamp and Duration ToString() calls don't throw

Fix bazel BUILD for Java.

Refactor README.md.

Move the original README.md to src since it's talking about C++
exclusively and add a more general README.md to document how
to install protoc for all languages.

Fix mistakes in highest-representable float64 integers

Avoid upcasting uninitialized pointers

Fixes google/protobuf#693

msan flags this as being undefined behavior. I think it's triggering
because the compiler has to insert a branch to avoid changing the
pointer's value if it starts out NULL. I can't figure out if this is
actually undefined behavior or not, but it definitely seems to be a gray
area of the standard which is best avoided.