Feature/migrate history

[delcroip]

Migration of the interactive user to a new history model (temporary), I only went to step 4, 5 and 6 will be fore later when all filter_validity would be replaced by Model.filter_validity

How to use:

# for migration of Versionned Model to openIMIS Model
# will keep the id as is but will rename the table column to id
# 1. change the base model of the class you want to use by OpenIMISMigrationModel and comment id and uuid
# 2. run `python manage.py makemigrations app_name` to update the table changes : rename and new column,
#    it will also create the history tablesrun `python manage.py makemigrations app_name --name to_history --empty`
# 3.
# 4. in that migration file, run MyModel.migrate_to_history() to move all the
#    record that have validitiy_to not null to history model
# 5. change the base model of the class you want to use by OpenIMISModel
# 6. run `python manage.py makemigrations app_name` to update the table changes : remove the validity_to and from

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
11466796	Triggered	Username Password	7b835d8	core/tests/test_graphql.py	View secret
11461807	Triggered	Generic Password	7b835d8	core/tests/test_graphql.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}