Upgrade from 1.6.x to 2.0.x leaves InterfaceRedundancyGroupAssociation fields defined incorrectly

[glennmatthews]

Environment

• Nautobot version (Docker tag too if applicable): 1.6.3 --> 2.0.2

Steps to Reproduce

1. Install Nautobot 1.6.x.
2. Create an InterfaceRedundancyGroup and associate Interfaces to it
3. Upgrade to Nautobot 2.0.2

Expected Behavior

• InterfaceRedundancyGroupAssociation.created should be a datetime rather than a date (this was acceptable in 1.6.x but is incorrect in 2.0.x where all created fields must be datetimes).
• InterfaceRedundancyGroup.status should not be nullable (this was a known bug in 1.x but was fixed for all other models in 2.0.x)

Observed Behavior

In the upgrade case (unlike the initial-install-with-2.0 case), InterfaceRedundancyGroupAssociation.created is incorrectly still a date field, and InterfaceRedundancyGroup.status is incorrectly still nullable.

This is because migration nautobot/dcim/migrations/0022_interface_redundancy_group.py differs between 1.6.x and 2.0.x in these areas, but is already applied in the 1.6.x installation and not reapplied in the migration to 2.0.x.

Any migration fix here needs to test and validate at least the following scenarios:

• Upgrade from 1.6.x to fixed version
• Upgrade from 2.0.2 to fixed version
• Initial install of fixed version