ETT-314 Remove apparently-unused template field from ht_institutions

[moseshll]

• Remove deprecated ht_proxies
• Remove ht_logs, ht_contacts, and ht_contact_types which now have an otis_ prefix
• Remove ht_institutions.template
  • Regenerate mysqldump of ht_institutions without template column.
  • This is the full dump, I believe the previous iteration was hand-crafted (with some columns excluded).
  • Prefer to use data that can be regenerated with a minimum of fuss, hoping to help mitigate schema drift.
  • ... as long as this does not expose sensitive data.

[aelkiss]

@moseshll Some of the data from ht_institutions makes me a little bit itchy -- maybe especially the list of IdPs for institutions that aren't enabled (these may be former members, members in testing, etc) -- certainly the IdPs for enabled ones is available via the wayf and the public institutions dump anyway so that stuff is fine. Likewise the specific scopes we allow per IdP I'm not sure about - again, I think this is probably OK at least for "enabled" ht_institutions. I might be inclined
to omit the institutions where enabled=0 - that might be a reasonable balance of ease of regeneration and not committing information that potentially shouldn't be public. (The one exception there is probably the hathitrust inst_id.) I'm also not really sure at this point for what purposes we even need this information in dbimage anyway (rather than just having the schema and adding fake data); better understanding that might change my position here.

[moseshll]

@aelkiss it's actually fine to have some custom "dump schemas" for lack of a better term. I'll restore the file with something more like the existing dump, and keep the code that creates it around for posterity next time we want to recreate the data.

Would it be too involved to close/delete this PR and erase the branch from history?

[aelkiss]

I think if we close the PR and delete the branch GitHub with garbage collect it. I don't think it's a major issue.

[aelkiss]

@moseshll Do we still want to close this PR and delete the branch?

[moseshll]

@aelkiss Closing and deleting. I have notes on what should be done as a follow-up.