Review the relevance of development tools in ODKFull

The _ODKFull_ image contains a lot of development tools (not _ontology_ development tools; _software_ development tools), such as:

* the entire stack to build C/C++ programs (basically the GNU Compiler Collection and all the associated tools; what Debian calls `build-essential`);
* the autotools;
* the stack to build Java programs (JDK + Maven);
* Subversion.

Those tools have been there since before I started using/developing the ODK, and I can’t help but wondering why.

Do people really compile C, C++, or Java programs as part of their custom workflows?

This is _not_ an announcement that those tools are going to be removed (yet), but I might seriously consider it at some point.

Start by locating the ODKFull image definition and reviewing where the listed C/C++, Java, autotools, and Subversion tools are installed or used. Done means documenting their relevance to custom workflows and reaching a clear decision about the scope of any removal.

Written by the indexing model from the issue text.