revert adding placetype column

[missinglink]

yesterday I merged #73 and today I decided that was possibly not a great idea. this PR reverts part of PR73.

I'm reverting the schema changes due to unnecessary duplication of data which is better normalized:

• the placetype should not be stored in the token table, it should belong in the docs table instead.
• each token row has a wofid column which can be joined to the docs table when this string is required.
• having an additional string column per row in the token table increases the disk requirement.
• schema changes require every consumer to update their data files to remain compatible.

If we get this merged today it will hopefully prevent anyone from being forced to upgrade due to the schema incompatibility.

[orangejulius]

Makes sense to me! Joins FTW. Any idea what the change in disk requirement was? I could imagine the performance impact of the JOIN being less desirable than the increase in storage, but that feels unlikely. Maybe worth checking out though, and its good to have options.

[missinglink]

@orangejulius the difference in filesize was 560M vs 535M for 1 extra column on 1.3 million rows.

I'll take care of reverting the master s3 bucket to the correct data