Core categories expansion

[drekar]

per https://www.pivotaltracker.com/story/show/155148554

[joshuarubin]

Yeah, this looks good as long as this is the approach we decide on long term. We'll have to ensure that our category ids match legacy stuff that @sesq is working on. Let's wait to merge until we have a joint plan.

[robert-uhl]

LGTM. I concur with @joshuarubin's comments.

[drekar]

After speaking with Ops, it looks like we want these categories not just to be available for use in Legacy, but to be immediately available in Legacy from the get-go. This presents a challenge because 1) adding new categories in legacy would require a nontrivial amount of development time and
2) we want to keep the codes equivalent in the two systems such that they remain being compatible
To facilitate this, the recommendation from @lnabarretezvelo is to redefine existing categories as such:

1. Reuse financeopt_4; make it cryptocurrency
2. Reuse netbeg_4; cryptojacking
3. Combine the four cat_ids that belong to Javascript, C/C++, Java, Visual Basic into one cat_id called "Programming Languages".
4. Then we have 4 spare; one can be used as blockchain. (edited)
5. Terrorism in legacy is being put into hate_4.
   This suggestion is being confirmed with the rest of Ops and Jay, so this PR is on hold until then, as the change will need to be backported into this package.
   This presents the risk that any existing clients who have hard-coded logic dependent on these repurposed category IDs (rather than category short names) will see unexpected behavior.

[joshuarubin]

category.go needs to be updated with the "long" description of the categories.
schema.graphql needs to be updated with the additions as well.

[joshuarubin]

We don't yet know that these are the final names of the categories, or that their IDs match legacy.

[coveralls]

Coverage remained the same at 9.786% when pulling 3143901 on core-categories-expansion into a055c76 on develop.

[joshuarubin]

@drekar @jbriggs-zvelo @zvbuhl can you take a look at these changes before I merge please?

[drekar]

This item is still on hold pending confirmation from Ops that the new category IDs will append vs. mutate existing. I have just been informed that they will most likely be appending to the end in alignment with the code changes alredy made herein, so we shouldn't need to do any more except for add the full names as @joshuarubin mentions.

[drekar]

Thanks @joshuarubin for the update to add the long names and update the api metadata. When we get the final OK from Ops confirming these IDs match theirs in legacy, this PR should be ready to merge!