Remove the `force_to_redownload` column on the registry tables

What does this MR do and why?

Several releases ago from last year, we deprecated the column named #force_to_redownload in these five tables:

1. design_management_repository_registry
2. group_wiki_repository_registry
3. project_repository_registry
4. project_wiki_repository_registry
5. snippet_repository_registry

The column was marked with ignore_column in the model definition per the process for avoiding downtime from removing columns. This MR updates the annotations for the current release version and date in the ignore_column definitions, and then establishes Geo DB migrations to drop the column from each of these tables.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

How to set up and validate locally

1. Run migrations on your geo secondary site up and down to verify they execute smoothly.

Questions for Reviewers

Since this is my first time pushing a migration to the Geo DB, I have a few questions for my reviewers:

1. Do I have to run the migrations and commit changes to my ee/db/geo/structure.sql? For some reason it seemed to radically change it on my dev environment relative to what's checked into source control.
2. Is there danger in changing the ignore_column milestone and date parameters to the current 16.9 release? And am I incorrect already ... should it now be 16.10 and next month's date?

Related to #417474 (closed)