Data Migration to Support New Discharge Reason Field

[Ashesh3]

Proposed Changes

This PR includes changes for migrating existing data to align with the newly introduced new_discharge_reason field in our database schema. The update ensures backward compatibility and seamless integration of the new field across various modules. The modifications are primarily focused on serializers, viewsets, and tests, ensuring that all functionalities related to patient discharge reasons are updated to use the new field. This change is pivotal for enhancing our data handling capabilities and providing more detailed reasons for patient discharge in our system.

Associated Issue

• Convert discharge_reason to IntegerField #1739

Phases for the change

1. Schema Changes
2. Migrating Data
3. Moving the temp field back to the original field and deprecate the temp field.

@coronasafe/care-backend-maintainers @coronasafe/care-backend-admins

[codecov]

Codecov Report

Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (ef73d93) 61.04% compared to head (870298b) 61.05%.

Files	Patch %	Lines
care/facility/api/serializers/shifting.py	33.33%	2 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1773   +/-   ##
=======================================
  Coverage   61.04%   61.05%           
=======================================
  Files         208      208           
  Lines       11526    11528    +2     
  Branches     1656     1656           
=======================================
+ Hits         7036     7038    +2     
  Misses       4218     4218           
  Partials      272      272           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Ashesh3]

@rithviknishad @sainak @vigneshhari could you review this PR once?

[Ashesh3]

@vigneshhari could you review this?