Consider disabling / removing "persons" class

[joepio]

• According to @baksand there are municipalities that were surprised to find the presence of their officials (employees) on openbesluitvorming. They'd rather not have these names in there. On the other hand, having names of council members could be valuable in some cases.
• Most resource views no longer work, because the id.openraadsinformatie API is no longer live. We only use elastic.
• Since our agreement with VNG only includes Document as class, other classes are technically no longer in scope.

I think the easiest solution is to deprecate the Persons class entirely, remove the data from the indexes. Disable the import. Perhaps even remove the code.

We could consider removing other classes, too, such as Commission and Reports.

@breyten what is your opinion on this?

[joepio]

@breyten and I discussed and decided that we'll leave the current data and classes in the back-end, and remove them from the front-end.

[joepio]

@robvandijk