This required, for some of the competitions, to run the data through
dos2unix, which changed the shas.  But also, at the etl library level,
we needed to remove the unicode <feff> character that sometimes gets
added to the start of the csvs.

This comes from an exterior sheet, and used for sorting.  Also included
a new CellProcessor for default values.

This updates the modern competitions to use the common deploy tooling,
which includes a decrypt helper function and the help documentation that
explains how to call the script.

There are a few legacy competitions which have not been updated, but
potentially could be in future.

Also included a template change where Attachments was forgotten

Just copied over from the template and replaced all the variables.

This should be a complete shell for a new competition, with some of the
documentation moved out of the base README.md.  With these instructions,
someone should be able to quickly get a new site up and running.

Nothing massive here, mainly just making the structure a bit deeper by
creating top level directories for the base install and the
competitions, then spliting up the docs a little.

Documentation about option included in the documentation in the diff..
There's also a small typo fix where -a was in the usage instead when
the option is -c

This passes through to the compose-and-upload files

As organizations evolve, so must the code.

This couldn't really be a diff, especially on compose-csvs/upload, because
the change was too massive.  So those files were deleted and a new one was
put in their place, even though it has some of the options processing
those did.

Issue #53: Refactor ETL code to create central utilities

This follows up to r16468 in the corporate repository.

These include:
* Adding editability to the project
* Adding LFC Analysis and Evaluations Tabs
* Adding LFC Analysis columns
* Adding Top 16 proposals processing - a list of proposals noted by LFC
* Adding LFC Consulting Parnters Group

Includes a new spreadsheet that was added in the ots subversion
directory.

This corresponds to r96 in the internal bigdata repository.

This required using the spreadsheet, and then culling proposals that
don't exist in it.

No surprises.  Justd encrypt, unzip, then add into the final spreadsheet
into new columns.

We're replacing the complex supplemental TOC with a more configurable
template that lives on the wiki.  Before, we were stretching the meaning
of a table of contents and the work being done by torque, and having
them do more than stictly necessary.  Now that configuration is in the
right place.

We moved things around in our internal tree, so update installation
paths here accordingly.

Though these aren't actually the "top 13", but rather 13 that the board
members were interested in.

Requires putting the attachments in the right place, and then creating
a new TOC and TOC template for these to add to a page they specified.

Also kept the list of what exactly are the top13 in svn to keep it
private.

This accidentally got two disparate changes in one, but they are:

Adding the lfc recommendations, which was a small spreadsheet with
just a classification of 25 proposals based on a document LFC produced
internally.

Also update thematic areas to have descriptions included.  This
coincided with some other changes requiring us to not overwrite the
pages on the wiki by default.

Because these pages were already on the wiki in a different location,
needed to update the toc deployment code to not also put out mwiki
files.  Only the TOC files for torque were needed.

There is an issue in gpg that CLI decryption with spaces fails.  So we
renamed the file in subversion, requiring a change here.

There were too many of the previous topic that we organized by,
so this custom list takes the place of that, also for the Topic_TOC.

Based on this review:
https://github.com/OpenTechStrategies/csv2wiki/pull/25

The name of the option was incorrect.

We add type information for the upload, and that was causing issues
where proposals were attempting (and failing) to get uploaded for the
second line that only had type information.

Initial checkin of all the work to get the EO2020 competition up and
running.

Before, this was handled manually, but in the new world, we script it
all from inside the ETL pipelines.  This adds that capability to the
2020 competition.