The usage of ICustomDiagnosticMessage here is non-essential - ToDiagnosticString
doesn't actually get called by ToString() in this case, due to JsonFormatter code. It was
intended to make it clearer that it *did* have a custom format... but then arguably I should
do the same for Value, Struct, Any etc.

Moving some of the code out of JsonFormatter and into Duration/Timestamp/FieldMask likewise
feels somewhat nice, somewhat nasty... basically there are JSON-specific bits of formatting, but
also domain-specific bits of computation. <sigh>

Thoughts welcome.

Introduce ICustomDiagnosticMessage to allow for custom string formatting

Fix compiler warning from repeated_field.h

Update podspec version to 3.0.0-beta-2

throw IOException instead of InvalidProtocolBufferException when appropriate

JSON Conformance improvements

Fixed Python 3.x C++ build, and updated conformance failure lists.

It's already submitted.

Fix tests broken by the Java directory change.

"valueField": null

is parsed appropriately, i.e. that it remembers that the field is set.

Previously we were incorrectly packing wrapper types.
This also refactors FieldCodec a bit as well, using more C# 6-ness.

Change-Id: I39c4eadbd28164cfd83aa2d1d8b6dfe8286db803

Restructuring protobuf to multiple modules

protobuf/java will become a parent pom that will contain two modules:

core - contains all of the code for the protobuf-java artifact
util - contains all of the code for the protobuf-java-util artifact

Also cleaned up various Maven warnings.

- Spot an Any without a type URL
- In the conformance test runner, catch exceptions due to generally-invalid JSON

This fixes issue #933, effectively.

Prohibit null values in maps

Allow conformance test runner to tolerate crashes, and re-enable conformance tests

Fix typos in README.md/CHANGES.txt

Release the semaphore in dealloc, fixing leak.